Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
2022.3.64f1
6000.0.53f1
6000.1.11f1
6000.2.0b9
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-111110
Regression
No
Project window selection is not updated when search term is changed
How to reproduce:
1. Open the attached “IN-107138” project
2. In the Project tab search bar, enter “t:prefab”
3. Select all visible assets
4. Without clearing the selection, change the search filter to “t:prefab test2”
5. Right click in the Project tab, select the “Delete” option
6. Click the “Delete” button
7. Change the search filter to “t:prefab”
8. Observe the Project tab
Expected result: Only the “test2” prefab was deleted
Actual result: All prefabs have been deleted
Reproducible with: 2022.1.0a1, 2022.3.64f1, 6000.0.53f1, 6000.1.11f1, 6000.2.0b9, 6000.3.0a1
Reproducible on: Windows 11
Not reproducible on: No other environments tested
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
- Texture generator reference image fails despite valid size
- Agent mode can enter infinite execution loop
- AI Gateway responses contain duplicated sentences
- Texture 2D asset is created when promoting a generated Cubemap to a new asset
- Unable to copy multiple paragraphs from Assistant responses
Resolution Note:
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.
Resolution Note (6000.5.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.