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

Status:	open

Project:	perforce-software-workshop

Severity:	B

ReportedBy:	thomas_gray

ReportedDate:	2015/10/09 09:35:01

ModifiedBy:	perforce

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

OwnedBy:	thomas_gray

Description:
	From @paul_allen:
	Another cool feature which is sort of related is to have a workspace setup for the user. 
	
	A simple button on the project home page that allows you to create a workspace and download a `.p4config` file.  The button would create a workspace spec for the user; auto generate a name using the users ID and project name, then calculate the View and set the Host to 'null' as that would be unknown.  You may need a popup to ask for the local 'root' for the workspace.  Then we create a '.p4config' file for the user to download (filling out P4PORT, P4CLIENT, etc...). 
	
	If you really want to push the boat out, then we could add a button to 'clone' the project using DVCS.

DevNotes:

Type:	Feature