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

Status:	open

Project:	perforce-software-p4connect

Severity:	B

ReportedBy:	norman_morse

ReportedDate:	2016/06/02 10:28:05

ModifiedBy:	norman_morse

ModifiedDate:	2016/06/02 10:28:05

Description:
	Rename failures are common.
	
	When renaming files within Unity often the rename operation will only be partly successful in Perforce. 
	Sometimes it works perfectly and both the asset file and its associated .meta file are renamed but other 
	times the asset is renamed correctly but its associated .meta file is not. 
	
	The .meta file is added in its new location but the old file is not deleted. 
	When this happens, the .meta file’s icon is the normal add icon rather than the rename (reversed) add icon.
	
	From internal case 00240697

DevNotes:

Type:	Bug