Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.34f1
2022.3.18f1
2023.2.8f1
2023.3.0b5
Issue ID
UUM-62700
Regression
No
The selected group of GameObjects do not get renamed when the new name matches one of the selected GameObjects
Reproduction steps:
1. Create a new project
2. Create an Empty GameObject
3. Create a few copies of the GameObject with different names
4. Restart the Editor
5. Select the created GameObjects
6. Using the Inspector window, rename the selected GameObjects to the name of one of the selected GameObjects
7. Observe the results
Expected results: The GameObjects successfully get renamed
Actual results: The names of the GameObjects don't change
Reproducible with: 2021.3.34f1, 2022.3.18f1, 2023.2.8f1, 2023.3.0b5
Reproducible on: Windows 11 Pro
Not reproducible on: No other environments tested
Notes:
- Does not reproduce when renaming without restarting
- Does not reproduce on newly created GameObjects if the Editor version is changed when restarting
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
- Palette Settings link to the documentation isn’t working
- Tags & Layers window has inconsistent remove button behaviour between Tags, Sorting Layers, and Rendering Layers when there are no removable items in the list
- "Type Options" and "Node Library" dropdowns do not open when clicked on the title
- Public char variables uneditable in Inspector when project setting "Use IMGUI Default Inspector" is enabled
- IAP Listener component’s list titles go out of bounds when resizing the Inspector window horizontally
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.