Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2022.2.14f1
2023.1.0b13
2023.2.0a9
2023.3.0a3
Issue ID
UUM-32946
Regression
No
UX: Prefab Family Popup terminology needs to be improved.
Prefab Family Popup:
"This Prefab doesn't have any children.
Prefab Variants created from this Prefab will be listed here."
->
Prefab Variants created from this Prefab will be listed here."
Also add a text if no Variant ancestors exists.
See forum thread about feedback: https://forum.unity.com/threads/view-prefabs-hierarchy-without-opening.1423578/
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
- Animator state transition preview clips are flickering when zooming in
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
- "DebugAllocatorMode" option changes when changed in another Editor instance
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 (2023.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.