Skip to content

Improve repository-provider selection UX (when adding a new Project) #5524

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jankeromnes opened this issue Sep 3, 2021 · 2 comments
Closed
Labels
component: dashboard feature: teams and projects [DEPRECATED] Please, use feature: organizations or feature: projects labels instead. meta: stale This issue/PR is stale and will be closed soon roadmap item: teams & projects type: improvement Improves an existing feature or existing code user experience

Comments

@jankeromnes
Copy link
Contributor

When adding a new Project, you need to select a repository, and first you need to select which Git provider you'd like to view repositories from.

Current UX

Screenshot 2021-09-03 at 14 10 29

There is an option at the bottom of the repository-owner dropdown to switch to a different Git provider.

Also, PR #5474 added a more visible change link next to gitlab.com.

Suggested improvements

#5474 (comment)

suggestion: I think using just the verb change could go unoticed and confuse some users. Following the discussion in #5120 (comment) and the second iteration of the designs for repository selection in #4948, we could use a more verbose message here or below the repositories list. What do you think?

Approach A Approach B Second iteration for repository selection
choose-a choose-b 127672398-8f3407b9-bccb-4b0a-8744-4686caab845c
@jankeromnes jankeromnes added user experience type: improvement Improves an existing feature or existing code roadmap item: teams & projects 🧑‍🚀 crew: teams and projects feature: teams and projects [DEPRECATED] Please, use feature: organizations or feature: projects labels instead. labels Sep 3, 2021
@jankeromnes
Copy link
Contributor Author

jankeromnes commented Sep 3, 2021

I think using just the verb change could go unoticed and confuse some users.

Personally (but this is very subjective), I find this link to be in the most noticeable spot, and I don't think it would confuse me.

When an app is in an unexpected state (e.g. it's showing me GitHub repositories when I actually want to select a GitLab repository) I tend to look for clues as to why it's in the wrong state. Here, that clue is the bold github.com text in the sub-title. Immediately after, I look for a way to change this wrong element. In the previous UI, I was stuck, because there is no control next to the "wrong" information (I eventually stumbled upon the link at the bottom of the dropdown by accident, but it's so "far removed" from the wrong element that I didn't initially find it). Having a direct control to "fix" the "wrong" information (i.e. github.com --> gitlab.com) is what I personally expect in this situation.

However, the "easiest choice in the world" is always slightly worse than "no choice needed by design". Here, if we can go for Second iteration for repository selection, that resolves 100% of the issue for me (i.e. no need to pick a provider, or even understand what a provider is in the first place -- just select the repository from a combined list 👍).

@stale
Copy link

stale bot commented Dec 14, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Dec 14, 2021
@stale stale bot closed this as completed Dec 24, 2021
@stale stale bot moved this to Done in 🍎 WebApp Team Dec 24, 2021
@jldec jldec moved this to Done in 🍎 WebApp Team Jan 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: dashboard feature: teams and projects [DEPRECATED] Please, use feature: organizations or feature: projects labels instead. meta: stale This issue/PR is stale and will be closed soon roadmap item: teams & projects type: improvement Improves an existing feature or existing code user experience
Projects
Archived in project
Status: Next iteration 🛹
Development

No branches or pull requests

2 participants