Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2020.1.0a6
Issue ID
1187137
Regression
Yes
[VCS] Local files can't be marked for Add via the VCS Context Menu
How to reproduce:
1. Create a new project in your prefered workspace and open it
2. Connect it to Perforce or PlasticSCM and uncheck the "Automatic Add" option
3. Create a new folder, right-click it and try to mark it for Add
4. Observe that the option is greyed out
Expected result: Files can be marked for add via the Context menu
Actual result: Files can't be marked for add via the Context Menu and the option is greyed out
Reproducible in: 2020.1.0a6,
Not reproducible in: 2020.1.0a5, 2019.3.0b5, 2019.2.7f2, 2018.4.10f1, 2017.4.32f1
Note: reproduces both with Perforce and PlasticSCM
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.1):
Fixed in: 2020.1.0a7