Alex,
The use case is purely around the user experience, and more specifically for
navigation.
In the current release, that user experience is messy. The buttons for
navigation are mixed in with the buttons for actions. For example: on the
details pages, SUMMARY (a navigation button) is next to PDF, SAVE, DELETE,
SUBMIT (actions). Also, there's no consistency: some pages don't have any
buttons, and the ones that do, have different buttons from page to page.
That obviously makes sense for the 'action' buttons (because they aren't
relevant on some pages) but the navigation should be able to be made
consistent, and separated from actions.
Specifically today, we're looking to have an experience where a user can
navigate from RUNNER to BUILDER and LOGOUT without having to type in a URL.
And the ability to navigate to BUILDER from RUNNER SUMMARY or DETAIL, and
the ability to navigate to RUNNER from BUILDER SUMMARY or DETAIL.
Thanks,
Mark