Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.3.0b10
6000.4.0a5
6000.5.0a4
Issue ID
UUM-129365
Regression
No
Hierarchy v2: [Correctness] "Create empty child" on unselected node selects parent node
Steps to reproduce:
- Open any project with hierarchy v2 turned on
- select one node and right click on a different node
3. select create empty child in the context menu
Actual results: A child node is created but parent node is selected and highlighted
Expected results: A child node is created and the child node should be selected and highlighted
Reproducible with versions:
6000.3,6000.4,6000.5
Not reproducible with versions:
Can’t test with versions:
Tested on (OS): mac, windows
Notes:
- Cannot reproduce on windows
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
- ScrollView clips content when under an ancestor that has a filter set
- "Retrieving array element that was out of bounds" error thrown when attempting to remove a column from a Multi-Column List View
- Multi-Column List View horizontal scroll resets to left most position when scrolling vertically
- Floating License is lost for concurrent jobs
- Warning "Failed to insert item" is logged when Assigning Project to Organization's Project in the Project Settings
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.