# 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/Problem]. Required. # Feature and Bug are common terms. # A Problem is suspected bug, or one without a clear # understanding of exactly what is broken. # # Release: Release in which job is intended to be fixed. Job: SDP-720 Status: punted Project: perforce-software-sdp Severity: B ReportedBy: amo ReportedDate: 2021/11/30 07:43:27 ModifiedBy: tom_tyler ModifiedDate: 2022/01/30 11:43:46 OwnedBy: amo Description: Allow the setting of server configuration in the db.config table. At present, the SDP stores settings in the environment 'outside' the database, and scripts like 'verify_sdp' rejects any in-database settings, stating things like this: Note: P4JOURNAL must be defined as a shell environment variable and must not set in db.config. It is increasingly common to define the configuration in the database rather than in the environment or with 'override' flags like '-J' in this case, as this helps ensure the server is started with the same parameters each time. Having to reconfigure a working Helix Core Server settings to allow the switch to SDP is a problem. DevNotes: 2021-01-30 ttyler: Changed status from open to punted. See comments. Type: Bug