Search Issue Tracker

By Design

Votes

0

Found in

6000.3.0b1

6000.4.0a1

Issue ID

UUM-115739

Regression

No

Hierarchy V2 Search Query Blocks always operate in Equal mode despite its Operator setting

-

Steps to reproduce:

  1. Open the attached project
  2. Open the SampleScene
  3. In the Search Window, open the 't=BoxCollider' query
  4. Observe that it returns 3 Objects from the Scene - 2 Cube objects match since they use BoxCollider, which is an exact match. And a Square since it has the BoxCollider2D component, and the BoxCollider Query Block Operator mode is set to 'Contains'
  5. In the Hierarchy window, add a search Query Block for BoxCollider
  6. Right-click on the Block -> Operator and make sure the mode is set to 'Contains'
  7. Observe Hierarchy results

Actual results: Hierarchy Search Query Block operates in Equal mode despite having its Operator mode set to Contains. This only returns the 2 Cube objects, leaving out the Square object

Expected results: Hierarchy Search Query Blocks return the same results as in the standalone Search Window

 

Reproducible with versions: 6000.3.0a2, 6000.3.0b1

Can’t test with versions: 6000.0.56f1, 6000.1.16f1, 6000.2.1f1, 6000.3.0a1 (Hierarchy V2 not available)

 

Reproducible with (OS): macOS 15.6.1, Ubuntu 24.04

  1. Resolution Note:

    This is a known limitation of the hierarchy window and how we filter across type. we have the same behavior as the old legacy hierarchy which assumed that t:<type> was a PERFECT match.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.