This page may contain information related to upcoming products, features and functionality.
It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes.
Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.
A few questions - when there is no agent selected I assume we want the main CTA to be select agent, but where would we expect this to link to? Also is there anything else we want to tell them in the subtext other than the Kubernetes Dashboard cannot be viewed with no agent selected?
@emilybauman, as far as I know, we are planning to link the dashboard only from the Environments with the selected agent. (We can also do it from the agent page in the future). With this behavior, this screen would be a rare error (but still possible). And we won't have a page to select an agent.
I am rethinking it now though As @shinya.maeda suggested, we can add a field user_access_authorized_agents to the user type. It will let us build a list of the agents available for the user. If we can have it, we might need two states:
no agents available (empty state)
list of the agents available for the current user.
When no agent is selected, we don't want to provide an agent selection yet.
Showing a list of available agents does not scale well and it would require
tremendous backend work with minimal value added.
I recommend an explanation of the workflow: Something along the lines of:
open an environment and open the dashboard from there. We can even have
visuals that support this message.
@emilybauman, I am not sure which environments to open when the user clicks "View environments". Can we suggest opening a project and navigating to the dashboard from the project's environment? Then we can link to the projects page.
@anna_vovchenko - Ahhh got it, I thought they'd be in a project already but I then remembered this page is at a higher level. We could do something like this:
@emilybauman Based on other pages of this sort, I think we can shorten the text a bit and lean a bit more on the documentation. That way we don't need to revisit this page if/when the navigation changes
I'd also suggest paring down the CTA to just View projects. Something like this:
No agent selected
You can select an agent from a project's environments page.
View projects | Learn more
What do you think? It's concise, but I wonder if it might be a bit too formal
@phillipwells - I like it, my only concern is finding the dashboard in the environments page isn't super clear (due to the fact everything is collapsed when you land on it). But I'm not sure if we have to go into that much detail here because we do have a learn more link.
All SUS-impacting issues need to have a proper severity label set.
Please add a severity label, remove the automation:ux-missing-labels label, and then reply to this comment briefly explaining your reasoning for providing this severity.
If you are not the DRI for this area and would like help determining the best severity, please @ the appropriate person for assistance.