Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.3.X, 2020.1.X
Votes
0
Found in
2019.3.0a8
2020.1.0b4
Issue ID
1233595
Regression
Yes
[VCS] Multiple options greyed out in context menu when right-clicking Assets folder
1. On a machine with PlasticSCM set up, create a new project.
2. Set the Version Control to PlasticSCM. (Project Settings -> Editor, or Project Settings -> Version Control depending on Unity version.)
2. Right click Assets folder -> Version Control -> Choose an option such as 'Mark Add'
Expected result: Most menu options are not greyed out and can be interacted with.
Actual result: Most menu options are greyed out. Cannot be interacted with.
Notes:
- Tested on MacOS.
- Issue appears to also occur on Windows.
- The only menu option that was greyed out before 2019.3.0a8 was 'Resolve Conflicts'.
- Test cases run on TestRail expect the functions of 'Get Latest' and 'Mark Add' using this method to be available.
- Can select all assets in the folder and then choose the menu options from there as a workaround.
Reproducible in: 2020.1.0b4, 2019.3.0b9, 2019.3.0a8
Not Reproducible in: 2019.2.13f1, 2019.3.0a1, 2019.3.0a7
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note (fix version 2020.2):
Verified and fixed in 2020.2.0a12
Resolution Note (fix version 2020.1):
Fixed and Verified in Unity 2020.1.0b9
Resolution Note (fix version 2019.3):
Fixed and verified in 2019.3.14f1