Search Issue Tracker

Fixed

Fixed in 6000.5.0a7

Won't Fix in 6000.3.X, 6000.4.X

Votes

0

Found in

6000.0.58f1

6000.2.6f1

6000.3.0b3

6000.4.0a1

6000.5.0a1

Issue ID

UUM-119687

Regression

No

[Hierarchy V2] Add new Query Block window contains a typo in the Hierarchy Search Area block

Hierarchy V2

-

Steps to reproduce:

  1. Open the attached project
  2. Open the SampleScene
  3. In the Hierarchy window, press the Add new Query block button
  4. In the new window, observe the Hierarchy Search Area block 

Actual results: Block is named "Hierarchy (hierarchyv 2)". Either containing unnecessary space between 'v' and '2' based on the block's tooltip - "hierarchyv2". Or the space is in the wrong position and the block title should spell "hierarchy v2"

Expected results: Hierarchy Search Area block does not contain typos

 

Reproducible with versions: 6000.3.0a2, 6000.3.0b3, 6000.4.0a1

Can’t test with versions: 6000.0.58f1, 6000.2.6f1, 6000.3.0a1 (Hierarchy V2 not available)

 

Reproducible with (OS): macOS 15.6.1

  1. Resolution Note:

    Fixed in Unity 6000.5.0a7

  2. Resolution Note (fix version 6000.5.0a7):

    Fixed in Unity 6000.5.0a7

  3. Resolution Note (6000.4.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.

  4. Resolution Note (6000.3.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.

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.