# 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:	job000293

Status:	open

Project:	perforce-software-p4api-net

Severity:	B

ReportedBy:	norman_morse

ReportedDate:	2015/06/02 15:33:02

ModifiedBy:	perforce

ModifiedDate:	2019/02/19 10:51:17

OwnedBy:	norman_morse

Description:
	Retrieving the Protection Table is broken.
	
	From internal case 00107793, customer states:
	
	https://swarm.workshop.perforce.com/projects/perforce-software-p4api-net/files/main/p4api.net/Repository.cs
	
	3368: public IList<ProtectionEntry> GetProtectionTable(Options options)
	3369: {
	3370: P4.P4Command protectCmd = new P4Command(this, "protect", true);
	3371: P4.P4CommandResult r = protectCmd.Run(options);
	3372: if (r.Success != true)
	
	When executing the GetProtectionTable() method on Windows, the API brings up a Notepad with the protections table in then returns null when notepad is quit.
	I modified my copy of the source like this, to make the method work again…
	
	
	3370: P4.P4Command protectCmd = new P4Command(this, "protect", true, "-o");
	
	This fix is similar to the TypeMap line
	
	3238: P4.P4Command typemapCmd = new P4Command(this, "typemap", true, "-o");

DevNotes:

Type:	Bug