# The form data below was edited by 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. 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: HI-5 Status: closed Project: perforce_software-helix-installer Severity: C ReportedBy: douglasawh ReportedDate: 2018/04/13 13:04:35 ModifiedBy: tom_tyler ModifiedDate: 2019/06/27 12:38:17 OwnedBy: douglasawh Description: Automatically delete (or rename) reset_sdp.sh "After the initial install, the reset_sdp.sh script should be removed." I read the above and thought...why don't we just delete it? Well, the initial answer is obvious: they may still be testing. Forcing the users to redownload the reset_sdp.sh seems better than overwriting their production system them. I suspect this falls under not being able to keep a root user from shooting themselves in the foot, but I think it's worth thinking about. I'd suggest auto delete after 90 days, possibly 60. One option that would keep someone from accidentally running a command in their history would be to change the name of the script after each run. Then you have reset_sdp.sh1 to "infinity". This is slightly irritating if you are testing, but adding a digit to your command doesn't seem too hard. It might be fun to see how many times you've reset things anyway. It may be that this is beneficial, but not worth the implementation effort. It's just thought. If there was a "super low" severity option, I'd pick that. :) DevNotes: Type: Feature