Search Issue Tracker
In Progress
Fix In Review for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
0
Found in
6000.0.62f1
6000.2.13f1
6000.3.0f1
6000.4.0a5
6000.5.0a1
Issue ID
UUM-127522
Regression
No
Assets appear unsorted when the Package Manager’s "Labels" filter is applied
How to reproduce:
1. Create a new project
2. Open the Package Manager
3. Go to the “My Assets” tab
4. Click on the “Filters” dropdown
5. Select any label under the “Labels” section
6. Observe the Package Manager window
Expected result: Only assets with the selected label are visible
Actual result: All assets are visible
Reproducible with: 2022.1.0a5, 6000.0.62f1, 6000.2.13f1, 6000.3.0f1 (820bc0c5f094), 6000.4.0a5, 6000.5.0a1
Reproducible on: macOS 15.3.2 (24D81) (M1 Max)
Not reproducible on: No other environments tested
Note: The steps for adding a label to an asset in the Asset Store are in the internal notes
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Some Build Profile settings do not remain checked when launching a project without the /Library folder through the command line
- TextMeshPro gradient tags render as literal text when using a font that contains only a part of the ASCII character set
- Small rectangles appearing in the corner of title text in Editor when System Font and Bitmap are selected in preferences
- The shortcut character is typed into the name field when a [Shift + <any alphanumeric key>] shortcut is used to create the asset from "Asset/Create"
- TextMeshPro ligatures broken when Font Style setting is changed from “Lowercase” to “Uppercase”
Add comment