Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.3.0b2
Issue ID
UUM-117580
Regression
No
Inconsistent field titles: "Technical Name" in "Export Package" pop-up vs "Name" in "Inspector" window
h5. How to reproduce:
1. Create a project
2. Window -> Package Management -> Package Manager
3. Click “+” and select “Create package”
4. Enter the package name and click the “Create”
5. Select the newly created package in the Package Manager window
6. Observe package fields in the "Inspector" window
7. Return to the Package Manager window
8. Click the "Export" button
9. Observe fields in the pop-up
h5. Expected results:
Field names should be consistent. It should be "Technical Name" when the inspector is in read only mode. When in edit mode, keep "name" since the technical name is split in 2 fields then.
h5. Actual results:
In the "Export Package" pop-up, we see the title "Technical Name", but in the "Inspector" window, we see the title "Name".
h5. Reproducible with:
6000.3.0a5, 6000.3.0b2
h5. Can't test with:
6000.3.0a4 as this build has "Export" functionality
h5. Tested on (OS):
M1 Max - Sequoia 15.6.1
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
We have confirmed the issue. However, the fix for it will not be prioritized in the near future, so we're closing this ticket. We might reopen this ticket if priorities change.