# 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: job000334 Status: open Project: perforce-software-p4convert Severity: B ReportedBy: norman_morse ReportedDate: 2015/08/13 16:50:28 ModifiedBy: perforce ModifiedDate: 2019/02/19 10:51:20 OwnedBy: norman_morse Description: Warnings generated for "CASE-SENSITIVITY ISSUE" are deceptive and should be more informative. Frequently a warning like this: 23:09:28,729 pool-1-thread-1 WARN com.perforce.svn.process.SvnProcessNode ... CASE-SENSITIVITY ISSUE: From node is missing from dataset; skipping! Please check case options and platform types. com.p4convert.p4.caseMode = NONE com.p4convert.p4.lowerCase = false Actually has to do with a node missing from the dataset, not just a Case Sensitivity issue. This error can also happen with filtered and/or corrupt subversion repositories. It would be much better to report the missing path and version. That way the user can diagnose the issue without requesting Subversion mini-dumps etc... I would like an error report like this: 23:09:28,729 pool-1-thread-1 WARN com.perforce.svn.process.SvnProcessNode ... From Node Missing From Dataset; Skipping! ... From Path: /path/to/file ... From Version: #### This could be a CASE-SENSITIVITY issue: Please check case options and platform types. com.p4convert.p4.caseMode = NONE com.p4convert.p4.lowerCase = false DevNotes: Type: Feature