Search Issue Tracker
Fixed
Won't Fix in 6000.0.X
Fixed in 6000.3.4f1, 6000.4.0b4, 6000.5.0a4
Votes
0
Found in
6000.0.55f1
6000.1.15f1
6000.2.0f1
6000.3.0a4
6000.4.0a1
6000.5.0a1
Issue ID
UUM-113340
Regression
No
ID is not capitalized the same in different areas in Search Window
Steps to reproduce:
- Create a new project
- Open Window > Search > New Window
- Press the Star button to open sorting dropdown
- Navigate to more and observe "Id" capitalization
- Toggle Table view at right bottom of the window
- Press "+" button to open Add Collums drop down
- Observe "ID" capitalization
\\
Actual results: ID is capitalized different in different dropdown menus
Expected results: ID is capitalized in same way in dofferent dropdown menus
\\
Reproducible with versions:
6000.0.55f1, 6000.1.15f1, 6000.2.0f1, 6000.3.0a4
Not reproducible with versions:
Can’t test with versions:
2022.3.65f1 - these settings not available
\\
Tested on (OS):
Macbook M1 MacOS Sequoia 15.5
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
- Font character thickness does not adjust properly in UI Toolkit text when changing Bold Weight in Font Asset
- Multiple "[...] is inaccessible due to its protection level" errors are thrown when opening project with Unity Version Control installed
- Font character thickness does not adjust properly in UI Toolkit text when changing Bold Weight in Font Asset
- Sorting icons are tiny and misaligned in Import Activity window
- The Undo system does not record HideFlags.HideInHierarchy changes
Resolution Note (fix version 6000.4.0b4):
Fixed in 6000.4.0b4
Resolution Note (fix version 6000.3.4f1):
Fixed in 6000.3.4f1
Resolution Note (6000.0.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.