# 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: job000352 Status: closed Project: perforce-software-p4connect Severity: A ReportedBy: colinbday ReportedDate: 2015/09/23 12:34:24 ModifiedBy: perforce ModifiedDate: 2019/02/19 10:51:21 OwnedBy: colinbday Description: Get latest from within Unity does not work. An exception is reported: Path '/...' is not under client's root '/Users/colinday/Deveopment/Spellbind/colin.day-main'. There appears no way to ever get path P4Connect is using (/...) into a workspace view because it does not reside within any depot which is usually in the form of something like //depotname/... //workspace-name/... http://www.perforce.com/perforce/r12.2/manuals/cmdref/o.views.html Forums are reporting this does not work on both Windows and OSX. http://forums.perforce.com/index.php?/topic/4368-path-c-is-not-under-clients-root/ DevNotes: Type: Bug