# 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: job000180 Status: closed Project: perforce-software-p4connect Severity: C ReportedBy: StuartHarrisonSumo ReportedDate: 2015/03/25 04:36:20 ModifiedBy: perforce ModifiedDate: 2019/02/19 10:51:09 OwnedBy: norman_morse Description: R.12101 complains about "Multiple plugins with the same name 'p4bridge'" Multiple plugins with the same name 'p4bridge' (found at 'Assets/P4Connect/Editor/p4bridge.dll' and 'Assets/P4Connect/Editor/x86/p4bridge.dll'). That means one or more plugins are set to be compatible with Editor. Only one plugin at the time can be used by Editor. This can be solved by removing P4Connect/Editor/p4bridge*.* after installing the package (note there appear to be *3* copies of p4bridge, in the root, in the x86 subfolder and in the x86_64 subfolder). Perforce server version "p4 -Ztag info" : ... serverVersion P4D/NTX64/2014.2/978861 (2014/12/19) P4Connect release (look at the bottom right corner of the Perforce Configuration window) : P4Connect 2.7 betaR.12101 Unity3d Version : Unity 5.0.0b22 (32 bit) Operating system version, 32bit or 64bit : Windows 7, SP1, 64 bit. DevNotes: Type: Bug