Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
3.3
Issue ID
HUBX-824
Regression
No
Unity Hub displays the Source Control badge when using a project which does not use Collaborate or Plastic SCM
How to reproduce:
1. Create a new Unity project
2. Select “Edit” → “Project Settings…” in the main menu
3. Select your organization
4. Click “Create project ID”
5. Select “Window” → “Plastic SCM” in the main menu
6. Click “Create workspace” twice
7. Create a second Unity project
8. Select “Edit” → “Project Settings…” in the main menu
9. Click “Use an existing Unity project ID”
10. Select the organization and project you used in Steps 3-4
11. Click “Link project ID”
12. Select “Yes” if prompted by a pop-up window
13. Observe the Hub
Expected result: No badge is displayed next to the second project’s title
Actual result: “SOURCE CONTROL” badge is displayed next to the second project’s title
Reproducible with: 3.3.0
Reproducible on: Windows 10
Note: Unity Hub may need to be restarted if the badge does not appear instantly after linking the project
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
We have confirmed the issue, however the fix for it will not be prioritized in the near future therefore closing this ticket. This ticket may be reopened if priorities changes.