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
- Animator State Labels are not Rendered correctly when using the Bitmap Renderer as the Default Editor Text Renderer
- LDR render target is used when HDR is enabled in URP and Recorder Source is set to 360 View
- Terrain Layer's changes are not added to the Undo history
- “IndexOutOfRangeException: Index was outside the bounds of the array.” error is thrown when large Text (TMP) GameObject Overflow field is set to Ellipsis
- The OnValidate method is not invoked when reverting changes on a Prefab Variant
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.