You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On both the Packages browse page and the Package details page, Location information is only displayed using a UUID. This is despite the fact that the Locations page itself does include a name for linked storage locations.
UUIDs are long and difficult for humans to remember or easily differentiate from other UUIDs. We should use the more human-friendly location name for display in Package-related pages in Enduro.
To Reproduce
Steps to reproduce the behavior:
Go to 'the Packages browse page - look at the locations listed in the Location column of the browse table
Click on a package to navigate to its details page. Look at the Location information in the Summary area
Now use the sidebar to navigate to Locations. Notice that a Location name is listed.
Expected behavior
We should use the more human-friendly location name for display in Package-related pages in Enduro.
Additional context
Ideally this would also:
Work for minIO locations
Potentially allow users with sufficient permissions to configure their own location names via the Enduro UI
However, both of these are longer-term features that can be handled in future iterations.
The text was updated successfully, but these errors were encountered:
Describe the bug
On both the Packages browse page and the Package details page, Location information is only displayed using a UUID. This is despite the fact that the Locations page itself does include a name for linked storage locations.
UUIDs are long and difficult for humans to remember or easily differentiate from other UUIDs. We should use the more human-friendly location name for display in Package-related pages in Enduro.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
We should use the more human-friendly location name for display in Package-related pages in Enduro.
Additional context
Ideally this would also:
However, both of these are longer-term features that can be handled in future iterations.
The text was updated successfully, but these errors were encountered: