# The form data below was edited by super-tom_tyler
# Perforce Workshop Jobs
#
#  Job:           The job name. 'new' generates a sequenced job number.
#
#  Status:        Job status; required field.  There is no enforced or
#                 promoted workflow for transition of jobs from one
#                 status to another, just a set of job status values
#                 for users to apply as they see fit.  Possible values:
#
#                 open - Issue is available to be worked on.
#
#                 inprogress - Active development is in progress.
#
#                 blocked - Issue cannot be implemented for some reason.
#
#                 fixed - Fixed, optional status to use before closed.
#                 
#                 closed - Issue has been dealt with definitively.
#
#                 punted - Decision made not to address the issue,
#                    possibly not ever.
#
#                 suspended - Decision made not to address the issue
#                    in the immediate future, but noting that it may
#                    have some merit and may be revisited later.
#
#                 duplicate - Duplicate of another issue that.
#
#                 obsolete - The need behind the request has become
#                    overcome by events.
#
#  Project:       The project this job is for. Required.
#
#  Severity:      [A/B/C] (A is highest)  Required.
#
#  ReportedBy     The user who created the job. Can be changed.
#
#  ReportedDate:  The date the job was created.  Automatic.
#
#  ModifiedBy:    The user who last modified this job. Automatic.
#
#  ModifiedDate:  The date this job was last modified. Automatic.
#
#  OwnedBy:       The owner, responsible for doing the job. Optional.
#
#  Description:   Description of the job.  Required.
#
#  DevNotes:      Developer's comments.  Optional.  Can be used to
#                 explain a status, e.g. for blocked, punted,
#                 obsolete or duplicate jobs.
#
# Component:      Larger projects may use this optional field to
#                 indicate which component of the project a given
#                 job is associated with.
#
#  Type:	  Type of job [Bug/Feature].  Required.

Job:	CBD-23

Status:	suspended

Project:	perforce-software-cbd

Severity:	C

ReportedBy:	tom_tyler

ReportedDate:	2017/05/17 12:18:51

ModifiedBy:	super-tom_tyler

ModifiedDate:	2017/05/17 12:23:39

Description:
	Implement flexbile feature toggles.
	
	Flexible means feature can be enabled globally, per-component,
	or in some cases more granular, e.g. per-stream.
	
	Example:  Make the versioning of the Remapped field
	(CBD-17) be configurable as always on, always off,
	or always on but limited to the main branch.

DevNotes:
	CBD-SOW-2

Type:	Feature