# The form data below was edited by robert_cowham # 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. May also provide # additional information such as the earliest release # in which a bug is known to exist. # # Component: Projects may use this optional field to indicate # which component of the project a givenjob is associated # with. # # For the SDP, the list of components is defined in: # //guest/perforce_software/sdp/tools/components.txt # # Type: Type of job [Bug/Feature]. Required. # # Release: Release in which job is intended to be fixed. Job: SDP-509 Status: closed Project: perforce-software-sdp Severity: B ReportedBy: amo ReportedDate: 2020/02/07 04:20:40 ModifiedBy: robert_cowham ModifiedDate: 2020/08/15 10:01:02 OwnedBy: amo Description: "sdp-administrator-guide.docx" needs to be removed or updated. The SDP is intended to assist in the administration of a Helix Core Server, and there are SDP_Guide docs for Windows and Unix that are expected to cover the administration and use of the SDP. It is unclear if 'sdp-administrator-guide' is intended to supplement or replace the other SDP Guide docs. Also, the 'sdp-administrator-guide' itself is clearly out-of-date. The 'main' copy was included in change 25245, which was the 2019.1 SDP release (change description starts "Released SDP 2019.1.25238 (2019/03/02). ") However, the document itself states "2018.1" and "first draft", and "(C) 2015-2018", so does not tie up with the SDP version with which it's been included. https://swarm.workshop.perforce.com/projects/perforce-software-sdp/files/main/doc/sdp-administrator-guide.docx https://swarm.workshop.perforce.com/projects/perforce-software-sdp/files/dev/doc/sdp-administrator-guide.docx DevNotes: Fixed with new AsciiDoctor versions of docs. Component: doc Type: Bug