# The form data below was edited by perforce # 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: job000294 Status: open Project: perforce-software-p4convert Severity: B ReportedBy: karl_wirth ReportedDate: 2015/06/03 04:07:27 ModifiedBy: perforce ModifiedDate: 2019/02/19 10:51:17 OwnedBy: karl_wirth Description: P4Convert: Initially uses environment user (SVN) Initially P4Convert picks up the P4USER from the environment and runs commands against the Perforce server before switching to the user in the config file: (P4USER=FRED) Perforce server info: 2015/06/03 11:33:35 pid 18054 FRED@noclient 127.0.0.1 [p4convert/PUBLIC.Main.12912] 'user-info' Perforce server info: 2015/06/03 11:33:35 pid 18054 FRED@noclient 127.0.0.1 [p4convert/PUBLIC.Main.12912] 'user-users' Perforce server info: 2015/06/03 11:33:35 pid 18054 FRED@noclient 127.0.0.1 [p4convert/PUBLIC.Main.12912] 'user-user -f -i' Perforce server info: 2015/06/03 11:33:35 pid 18054 p4-user@noclient 127.0.0.1 [p4convert/PUBLIC.Main.12912] 'user-depots' Perforce server info: 2015/06/03 11:33:35 pid 18054 p4-user@noclient 127.0.0.1 [p4convert/PUBLIC.Main.12912] 'user-depot -i' This causes the following error when protections stop the user from being created: Caught exception on exit com.perforce.p4java.exception.AccessException: Access for user 'FRED' has not been enabled by 'p4 protect'. DevNotes: Type: Bug