Search Issue Tracker
By Design
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.2.0a1
2019.3.0a1
2020.1.0a1
2020.1.0a4
Issue ID
1184550
Regression
No
[VCS] Various VCS actions are not greyed out in the VCS Context menu for non-checked out Folders
How to reproduce:
1. Create a new project in your preferred workspace
2. Connect it to Perforce
3. Create a new folder and submit it
4. Right-click the folder and check the version control context menu for "Mark Add", "Get Latest", "Submit...", "Revert", "Lock" and "Unlock" options
Expected result: "Mark Add", "Get Latest", "Submit...", "Revert", "Lock" and "Unlock" are disabled/greyed out for all submitted/non-checked out assets
Actual result: "Mark Add", "Get Latest", "Submit...", "Revert", "Lock" and "Unlock" are enabled for submitted/non-checked out folders
Reproduced in: 2020.1.0a4, 2019.3.0b4, 2019.2.6f1, 2018.4.9f1, 2017.4.32f1
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
- Some GameObjects in a subscene are not rendered when using custom shaders and ECS until the Game view resolution changes
- Crash on AudioManager::InitFMOD when performing various actions in the Editor
- webGLBuildSubtarget resets to Generic when it gets changed in build script
- Publishing Settings are shared across different custom Build Profiles when modifying Build options
- deltaTime and unscaledDeltaTime discrepancy when Player window is moved to secondary monitor and VSync is enabled
Resolution Note:
For this moment this behavior is by design, because some operations like Check out, Add, Revert should be always available for folders because it is a recursive operation on a folder and it could cause performance issues when checking if any of these operations are available.