Search Issue Tracker
By Design
By Design in 1.7.X
Votes
0
Found in [Package]
1.7.0
Issue ID
AMATB-15
Regression
No
Unable to select multiple Collections in Asset Manager window using Shift key
Steps to reproduce:
1. Install Asset Manager package via Package Manager
2. Open Asset Manager Window (Window > Asset Manager)
3. In left navigation bar select project
4. Right-click on a project
5. Select “Create new collection”
6. Press Enter to create collection
7. In the navigation bar create multiple Collections
8. Try selecting created Collections holding Shift on keyboard
Actual results: unable to select multiple created Collections with Shift key (for example to select multiple Collections and delete them)
Expected results: able to select multiple Collections with Shift key
Reproducible with versions: 1.7.0 (6000.0.58f1, 6000.2.4f1, 6000.3.0b2)
Tested on (OS): macOS Silicon, Sequoia 15.6 (M1)
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
- 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
- Resize to Fit option for Import Activity window's Columns does nothing
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 (1.7.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.