# 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-17 Status: closed Project: perforce-software-cbd Severity: C ReportedBy: tom_tyler ReportedDate: 2017/05/17 12:18:21 ModifiedBy: super-tom_tyler ModifiedDate: 2017/05/17 12:18:23 OwnedBy: tom_tyler Description: Version 'Remapped:' and 'Ignored:' fields. The initial CBD implementation updated only the 'Paths:' and 'Description:' fields in the live Stream Spec when the versioned form, the *.cbdsst file, was updated. The 'Remapped:' and 'Ignored:' are ignored. That functions as initially designed, based on the "miminally intrusive" philosphy to avoid unnecessary impact of the custom CBD logic. However, later it was deeemd better for all aspects of the stream spec to be dictated by the versioned from of the file if we're going to have one at all, so they can go through the same merge down/copy up flow as Paths updates. DevNotes: CBD-SOW-2 Type: Feature