Skip to content
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

Cannot add a new project when having two accounts #6268

Closed
laushinka opened this issue Oct 18, 2021 · 7 comments · Fixed by #6484
Closed

Cannot add a new project when having two accounts #6268

laushinka opened this issue Oct 18, 2021 · 7 comments · Fixed by #6484
Assignees
Labels
feature: teams and projects [DEPRECATED] Please, use feature: organizations or feature: projects labels instead. groundwork: in progress needs visual design team: webapp Issue belongs to the WebApp team user experience

Comments

@laushinka
Copy link
Contributor

laushinka commented Oct 18, 2021

Bug description

When trying to add a new GitLab project under gitpod.io/new, I could not move forward and received no error messages. Supposedly this is caused by having two Gitpod accounts.

https://www.loom.com/share/ba9d0b291d1e491baafe7a1bd7db9ed3

Steps to reproduce

As the above video:

  1. Have GitHub and GitLab accounts.
  2. Log in via GitHub.
  3. Go to https://gitpod.io/projects and click "New Project"
  4. Click on the "change" link (to add a GitLab project)
  5. Click on "Continue with GitLab"
  6. You should see a modal pop up and then disappear. Nothing else will happen.

Workspace affected

No response

Expected behavior

I expect to be able to add a project, or see a helpful error message.

Example repository

No response

Anything else?

No response

@laushinka laushinka added user experience feature: teams and projects [DEPRECATED] Please, use feature: organizations or feature: projects labels instead. team: webapp Issue belongs to the WebApp team labels Oct 18, 2021
@laushinka laushinka changed the title Adding a new project when having two accounts Cannot add a new project when having two accounts Oct 18, 2021
@AlexTugarev
Copy link
Member

@gtsiolis, how to render errors on the "Select Git Provider" page of New Project wizard? Do we have some visuals for that? 🙏🏻

@JanKoehnlein
Copy link
Contributor

/schedule

@roboquat
Copy link
Contributor

@JanKoehnlein: Issue scheduled in the meta team (WIP: 0)

In response to this:

/schedule

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@JanKoehnlein
Copy link
Contributor

/assign @gtsiolis

@jldec
Copy link
Contributor

jldec commented Oct 26, 2021

Becuase this only impacts a subset of users, this is lower priority cc: @JanKoehnlein

@gtsiolis
Copy link
Contributor

Nice catch @laushinka! ⚾

Ideally, we would automatically associate these accounts, see #5975. Cc @AlexTugarev because #5975 (comment). 🧙

Following the pattern used in the login page (see #3950), we could re-use it here below the provider selection, see early design specs below using an updated component design.

Login Page Provider Selection Page
Screenshot 2021-10-26 at 11 39 29 PM Error

❗ The risk here is that we can not just prompt users to select a different provider as they are already logged in. Possible copy we could use here for the alert title:

  1. Gitpod account already exists
  2. Selected provider already in use

@AlexTugarev what do you think?

@AlexTugarev
Copy link
Member

@laushinka and @gtsiolis, in such a case rendering of a useful message is a great idea.

@AlexTugarev AlexTugarev linked a pull request Nov 1, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: teams and projects [DEPRECATED] Please, use feature: organizations or feature: projects labels instead. groundwork: in progress needs visual design team: webapp Issue belongs to the WebApp team user experience
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants