# 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: job000531 Status: closed Project: perforce-software-p4connect Severity: B ReportedBy: norman_morse ReportedDate: 2016/06/02 10:39:43 ModifiedBy: perforce ModifiedDate: 2019/02/19 10:51:34 OwnedBy: liz_lam Description: Configuration Asset doesn't work if project assets are not in default location. If P4Connect is not put in its default location (Assets/P4Connect) then it will throw the following exceptions Parent directory must exist before creating asset at Assets/P4Connect/Editor/Config.asset. UnityEditor.AssetDatabase:CreateAsset(Object, String) P4Connect.Config:WriteConfigAsset() P4Connect.ConfigWindow:OnGuiStatusBar() (at c:/tmp/64590263/depot/main/p4-connect/src/P4Connect/P4Connect/P4Connect.ConfigWindow.cs:422) P4Connect.ConfigWindow:OnGUI() (at c:/tmp/64590263/depot/main/p4-connect/src/P4Connect/P4Connect/P4Connect.ConfigWindow.cs:1027) UnityEditor.DockArea:OnGUI() UnityException: Creating asset at path Assets/P4Connect/Editor/Config.asset failed. P4Connect.Config.WriteConfigAsset () P4Connect.ConfigWindow.OnGuiStatusBar () (at c:/tmp/64590263/depot/main/p4-connect/src/P4Connect/P4Connect/P4Connect.ConfigWindow.cs:422) P4Connect.ConfigWindow.OnGUI () (at c:/tmp/64590263/depot/main/p4-connect/src/P4Connect/P4Connect/P4Connect.ConfigWindow.cs:1027) System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) (at /Users/builduser/buildslave/mono/build/mcs/class/corlib/System.Reflection/MonoMethod.cs:222) From internal case 00240703 DevNotes: Type: Bug