Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.1.20f1
2022.2.0a2
Issue ID
UUM-21679
Regression
Yes
Hierarchy doesn't keep the correct order after Undo and Redo commands
How to reproduce:
1. Open the user-attached project “BugTest1”
2. Open the “SampleScene” scene
3. Under the GameObject Root → Child B, put GameObject Child B11 on the top of child GameObjects of the Root GO
4. Press Ctrl + Z to Undo and then Ctrl + Y to Redo
5. Observe the GameObjects order
Expected result: Child B11 is the first GO under the Root
Actual result: Child B11 is the last GO under the Root
Reproducible with: 2022.1.0a12, 2022.1.20f1, 2022.2.0a2
Not reproducible with: 2020.3.41f1, 2021.3.12f1, 2022.1.0a11, 2022.2.0a3, 2022.2.0b12, 2023.1.0a15
Reproducible on: Windows 11 Pro
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
- [VFX] Custom HLSL with 'int' parameter, without the 'in/out/inout' access modifier is not supported
- [Windows] Lens Flare doesn't work in the Lens Flare Showroom URP Sample Scene
- Crash on ujob_execute_job while using OverlapBoxCommand when collisions are more than maxHits
- The validity of the multiple handles can behave differently based on the load/release operations order, when multiple Addressables.LoadAssetAsync and Addressables.Release are used to load and release the same Addressable Asset
- OnPointerExit and OnPointerEnter is mistakenly called when an overlapping child Image is destroyed
Resolution Note:
Issue should be fixed in latest 2022.2 and 2023.1, please upgrade to a newer version as 2022.1 is not longer supported.