Search Issue Tracker
Fixed in 2020.1
Votes
0
Found in
Issue ID
1195521
Regression
No
[VCS] Workflow: Moving assets should be optionally allowed even when they are marked for delete (or checked out etc.) remotely
In most normal cases, something being checked out or marked for delete remotely should prevent operations like renaming or moving an asset locally. That's what Unity does today.
However in some cases, a user option (like a confirmation dialog or an editor user setting) would be nice to override this. Scenario:
1. There's a big production going on using Perforce,
2. Someone marks a whole folder for deletion locally, by accident, and goes on vacation,
3. No one else can now rename or move files in Unity! P4V allows doing it, but Unity goes "oh no, marked remote for deletion, can't do it".
It should allow it, but perhaps with a confirmation dialog.
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
- Rendering is broken with UIToolkit with many Intel GPUs (driver-bug)
- [Vulkan] Crash in Windows Standalone when Vulkan is set as rendering API and player window is out of focus
- [Particle System] Editor freezes when assigning a nested Particle System in the Sub Emitter Module
- Unable to switch to different material when selecting another material from Asset selector window on Particle System Material
- Inspector displaying wrong characters when using ANSI encoding and non latin characters in a Shader property
CarolRogers
Aug 22, 2020 08:18
If you wan tot moves your assets then I would suggest you move with the following website https://bestmoversdmv.com/ . It will be convenient as they have all the required equipment.