Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.0.65f1
6000.3.4f1
6000.4.0b4
6000.5.0a4
Issue ID
UUM-132214
Regression
No
The Undo system does not record HideFlags.HideInHierarchy changes
How to reproduce:
1. Open the attached “IN-130283” project
2. Open the “Assets/Repro.unity” Scene
3. In the Hierarchy, select the “Component Test” GameObject
4. Lock the Inspector window
5. In the Inspector, right-click on the “Component Test” Component and select the "Record 2" option multiple times
Actual results: The scene doesn't show unsaved changes and can not undo the HideFlags change
Expected results: The scene gets dirty and its possible to save unsaved changes and undo the HideFlags change
Reproducible with: 2023.1.0a3, 6000.0.65f1, 6000.3.4f1, 6000.4.0b4, 6000.5.0a4
Reproducible on: macOS 26.2
Not reproducible on: No other environments tested
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.