Search Issue Tracker
By Design
By Design in 1.7.X
Votes
0
Found in [Package]
1.5.1
1.6.0
1.7.0
Issue ID
AMATB-28
Regression
No
Asset status label shows as "InReview" instead of "In Review"
Steps to reproduce:
- In the Asset Manager dashboard, an asset with "In Review" should be created
- Create a new Unity project
- Install the "Asset Manager" package
- Open Asset Manager window (Window -> Asset Manager)
- Select the same asset that was created in the dashboard
- Verify how its status is displayed in the asset details window
- Verify how status is displayed in "Add Filters ->Status" list
Actual results: "InReview"
Expected results: The status should be "In Review". It should be consistent in all the places
Reproducible with versions: 1.5.1, 1.6.0, 1.7.0 (6000.0.58f1, 6000.2.6f1, 6000.3.0b3)
Tested on (OS): macOS - 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
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- Module installation fails with "Download failed: Validation Failed" errors when using beta.2 Hub version
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Shader Graph Category dropdown cannot be expanded/collapsed when clicking on the text
- Different text alignment in the column header in Entities "System" window
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 (1.7.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.