Search Issue Tracker
Fixed in 2018.3.X
Votes
6
Found in
2017.4.1f1
Issue ID
1025002
Regression
Yes
[VCS][PlasticSCM] Folder move and rename operations aren't handled correctly
Steps to reproduce:
1. Open attached project in PlasticSCM workspace
2. Enable PlasticSCM in editor settings
3. In project window, drag Folder1 outside Folder2 to Assets folder
4. Notice that dragged folder's status is local although it should be tracked as it was just moved
5. In version control window, submit change and notice error (which also has wrong path):
PlasticSCM : There are no changes in the workspace c:\Users\juliusj\wkspaces\epo_zero
Note: on 2017.4 error is:
PlasticSCM : The item /FolderIssue/Assets/Folder2/Folder1.meta is not changed in current workspace
Doesn't repro on perforce or when moving assets instead of folders
Reproduced with: 2018.2.0a8, 2018.1.0f1, 2017.4.1f1, 5.1.0f3
Not reproducible: 5.0.4f1
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
JesusM
Jun 19, 2018 09:41
Hi,
Just to clarify the issue: it is a problem in the unity layer that does not send the "rename/move" request for a folder to the underlying SCM (Plastic in this case).
Perforce is not affected by this issue because it doesn't have directory versioning.