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
Have you considered alternative solutions to your feature request?
No.
Related problems
Is your feature request related to any problems? Please help us understand if so, including linking to any other issue tickets.
The UI/UX team had originally designed the UI's navbar to have categories to help organize links in the navbar and make it easier for users to find what they are looking for.
In addition, we expect the health API to include services (e.g. APIs, etc.) that a user wouldn't typically navigate to in a browser. So, we would need to know which of those items returned by the health API endpoint are items that have a UI the user should access.
Here is an example screenshot of the originally proposed navbar design:
Describe the feature request
The UI/UX team would like to propose the addition of two new fields that when filled in, helps bucket components into meaningful categories in the UI's navbar and help inform us of what should be added to the navbar as a navigable item. The values set in this field should be restricted to a specific set of values and those listed below are to get the conversation started on what the values should be.
@rtapella Please chime in on what I have posted above to ensure the accuracy of the request and fill in any missing details, and if we want to add/change the list of possible values for each of the fields.
The text was updated successfully, but these errors were encountered:
And we also would like to be able to know which items returned by the endpoint should be added to the navbar so that the health endpoint isn't restricted to only reporting on services that a user can navigate to in a browser.
Only those components that have their componentType set to ui would be added to the navbar. In addition, on the health dashboard, we could potentially add these two fields listing the components category and type.
@anilnatha I'm not yet sure if we can complete this in 24.4, but I think it's probable. I just think there are some other larger higher priority tickets still in the kitchen currently
Checked for duplicates
Yes.
Alternatives considered
No.
Related problems
The UI/UX team had originally designed the UI's navbar to have categories to help organize links in the navbar and make it easier for users to find what they are looking for.
In addition, we expect the health API to include services (e.g. APIs, etc.) that a user wouldn't typically navigate to in a browser. So, we would need to know which of those items returned by the health API endpoint are items that have a UI the user should access.
Here is an example screenshot of the originally proposed navbar design:
Describe the feature request
The UI/UX team would like to propose the addition of two new fields that when filled in, helps bucket components into meaningful categories in the UI's navbar and help inform us of what should be added to the navbar as a navigable item. The values set in this field should be restricted to a specific set of values and those listed below are to get the conversation started on what the values should be.
componentCategory
administration
,catalogs
,development
,infrastructure
,processing
componentType
api
,ui
,service
Example:
@rtapella Please chime in on what I have posted above to ensure the accuracy of the request and fill in any missing details, and if we want to add/change the list of possible values for each of the fields.
The text was updated successfully, but these errors were encountered: