UX: Jira integration should support OAuth
Problem to solve
Allow Jira users to authenticate with their Atlasssian credentials (OAuth) in order to setup the Jira integration in GitLab.
As described in the epic &4954
As an individual user, I want to use those Atlassian credentials to...
- View a list of Jira issues, so that I'm only viewing the issues I have access to.
- View the details of the Jira issue, so I can understand the full context of the item.
- Comment on issues, to participate in the discussion of the work.
- Edit/manipulate the details of the issue, such as changing the description, adding labels, and setting the status.
In addition to the user stories mentioned which are specific to: #220999 (closed) – more questions need to be answered before hand. For example, how and where should these Atlassian credentials be managed in GitLab? and how should cases like this be handled:
- What if the Atlassian user has access to multiple Jira instances?
- What if the Atlassian user is settings up an instance/group level integration?
- What happens when an Atlassian user's credentials change in scope or are revoked?
Proposal
- Add an additional method to authenticate using Jira Cloud OAuth
- After successfully authenticating, provide a success message that mentions where to go in order to manage/disconnect the OAuth
For this first MVC we will focus on Jira Cloud. In future iterations we should add support for Jira Server.
Additional user stories to consider
- Ensure that I am connecting the correct Jira instances/projects to GitLab (since I have more than one) so that I am only adding the information I need in GitLab.
- Remove my Atlassian credentials/access from GitLab so that I can sign into GitLab as a different Atlassian user.
Note: This issue was broken down from #284977[Proposal_auth_update.png]
Edited by Libor Vanc