# The form data below was edited by norman_morse
# Perforce Workshop Jobs
#
#  Job:           The job name. 'new' generates a sequenced job number.
#  Status:        Job status; [open/closed/suspended].  Required
#  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.
#  Type:	  Type of job; [Bug/Feature].  Required.

Job:	job000146

Status:	closed

Project:	perforce-software-p4connect

Severity:	B

ReportedBy:	p4pzp

ReportedDate:	2015/02/05 17:14:30

ModifiedBy:	norman_morse

ModifiedDate:	2015/03/23 16:55:43

OwnedBy:	p4pzp

Description:
	Per-project Perforce settings
	
	"It would be useful if you could have per-project perforce settings, if you have a different workspace for each project, or if you connect to different servers."
	
	Request from a reviewer/user from the Unity Asset Store

DevNotes:
	This is a feature of P4Connect 2.7 BETA.   
	
	You can create a configuration asset which will localize your settings.  This way you can have multiple projects
	on the same machine, talking to different servers and workspaces if you wish.

Type:	Feature