Search Issue Tracker
Won't Fix
Won't Fix in 2022.1.X
Votes
0
Found in
2021.3.3f1
2022.1.1f1
Issue ID
UUM-922
Regression
Yes
[Backport] An incorrect number of results is displayed in the search window when the user selects the search criteria "t: textur
To reproduce:
1. Open HUB;
2. Create a new project;
3. In "Assets" folder create a new one and name it "ArtWork";
4. Double click on "ArtWork" folder and verify that it is empty;
5. From added files move "sprite-sheets" and "sprites" folder to it;
6. Double click on a "sprites" to open it;
7. Verify that it has 11 items;
8. Go back to "ArtWork" folder and double click on "sprite-sheets" folder to open it;
9. Verify, that it has 2 items;
10. Click on a "Open in Search"and select "t:texture" option from the provided list or manually enter mentioned option;
11. Verify that results become displayed on the screen.
Expected result: Search window title and tab title should display 13 next to them - "Search (13)".
Actual result: Instead of "Search (13)" we get "Search (12)" in both mentioned places even though we see "13" next to "All" and next to "Project" tabs.
Reproduced on Unity: 2022.2.0a5, 2022.1.0b11, 2021.2.15f1- 2021.2.3f1.
Could not reproduce on Unity 2022.2.0a7, 2022.2.0a6, 2021.2.0f1, 2021.2.1f1, 2021.2.2f1.
Note: 2022.2.0a6 seems is fixed from this version.
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
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- Module installation fails with "Download failed: Validation Failed" errors when using beta.2 Hub version
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Shader Graph Category dropdown cannot be expanded/collapsed when clicking on the text
- Different text alignment in the column header in Entities "System" window
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (2022.1.X):
There are no fixes planned for this Bug