Search Issue Tracker
Fixed in 2020.1.X
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.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Add comment