Search Issue Tracker
By Design
By Design in 6000.6.X
Votes
0
Found in
6000.5.0a8
6000.6.0a1
Issue ID
UUM-135926
Regression
No
Sort label is misleading when sorting Samples by Name in All Samples tab
Steps to reproduce:
- Create a new project using Universal 3D template
- Open the Package Manager (Window > Package Management > Package Manager)
- Open the "All Samples" tab
- Click on the "Sort:" dropdown and choose "Name (asc)" or "Name (desc)"
- Observe the ordering of the listed Samples
Actual results: Entries are grouped and ordered by Package Name first and only then by Sample Name, so the overall list is not globally sorted by Sample Name
Expected results: Either entries are sorted globally by Sample Name in asc/desc order, or the sort dropdown clearly indicates that sorting is primarily by Package Name (for example via separate “Sort by Package Name” and “Sort by Sample Name” options)
Reproducible with versions: 6000.5.0a8
Can’t test with versions: 6000.0.70f1, 6000.3.10f1, 6000.4.0b11, 6000.5.0a7 (Samples tab does not exist)
Tested on (OS): Windows 11
Notes:
- The most prominent text in each row is the Sample Name, so the “Sort: Name” label appears to refer to that, even though the primary sort is by Package Name
- Grouping by Package may be intentional; this report is about the ambiguity of the sort label and options rather than the grouping itself
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
- Performance Markers Search window shows an empty entry in the list
- Enabling Deep Profiling in Performance Markers Search window breaks Inspector panel buttons when navigating through the marker items
- Dragging selector from selector row background shows preview but does not apply class in UI Builder
- An "InvalidOperationException" error is thrown when TryRemoveItem is used with rebuildTree set to false
- Build fails with IL2CPP error when building on Android platform in a specific project
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.6.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.