# 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: job000218 Status: closed Project: perforce-software-p4convert Severity: A ReportedBy: tardis ReportedDate: 2015/04/28 09:41:25 ModifiedBy: perforce ModifiedDate: 2019/02/19 10:51:13 OwnedBy: tardis Description: Subversion tags with spaces in name result in crash when label conversion is on: com.perforce.p4java.exception.RequestException: Error in label specification. Error detected at line 1. Wrong number of words for field 'Label'. at com.perforce.p4java.impl.mapbased.server.Server.handleErrorStr(Server.java:4909) at com.perforce.p4java.impl.mapbased.server.Server.createLabel(Server.java:1101) at com.perforce.common.label.LabelImport.(LabelImport.java:72) at com.perforce.common.process.ProcessFactory.getLabel(ProcessFactory.java:88) at com.perforce.common.process.ProcessLabel.labelChange(ProcessLabel.java:52) at com.perforce.svn.process.SvnProcessNode.processDir(SvnProcessNode.java:455) at com.perforce.common.process.ProcessNode.process(ProcessNode.java:50) at com.perforce.svn.process.SvnProcessChange.processChange(SvnProcessChange.java:179) at com.perforce.common.process.ProcessChange.runSingle(ProcessChange.java:90) at com.perforce.common.process.ProcessChange.call(ProcessChange.java:53) at com.perforce.common.process.ProcessChange.call(ProcessChange.java:20) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) DevNotes: Type: Bug