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

Status:	open

Project:	perforce-software-p4api-net

Severity:	C

ReportedBy:	QAP

ReportedDate:	2015/12/15 08:04:05

ModifiedBy:	perforce

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

OwnedBy:	QAP

Description:
	When connecting, one can specify either (A) the current working directory or (B) the [port, client, user, password] quadruple, but not both. As a result, it's not currently possible to implement the equivalent of the following command-line using P4API.NET:
	
	  set P4CONFIG=p4config.txt
	  echo P4USER=bdylan > /some/path/p4config.txt
	  p4 -d /some/path -c myClient [COMMAND]
	
	which would result in:
	* P4USER = bdylan (set via P4CONFIG)
	* P4CLIENT = myClient (set via command-line switch)
	
	See https://swarm.workshop.perforce.com/files/guest/perforce_software/p4api.net/p4api.net/Connection.cs, method Connect(), the "if" block starting at line 223.
	
	In P4API.NET, I can call:
	
	(A) Connection.Connect(new Options { "cwd" : "/some/path" }) in which case I'll run with the CurrentWorkingDirectory set to /some/path, will find the p4config.txt file in that directory, and will set P4USER to bdylan. I can't specify the client/user/password unless I put them into the config file. (This uses the 1-parameter P4Server constructor.)
	
	(B) Connection.Connect(null) in which case I'll make use of the Server/UserName/Client that I've set up. However, in this case I won't find p4config.txt. (This uses the 4-parameter P4Server constructor.)
	
	It would be nice to allow utilising both (A) the "cwd" and (B) the Server/UserName/Client properties. In fact, there already is a 5-parameter P4Server constructor that could be used for this so this may not be too complicated...

DevNotes:

Type:	Feature