Skip to content

Draft: Add support for self-managed GitLab for Jira app

Tom Quirk requested to merge 356361-integrate-fe-be into master

What does this MR do and why?

The final MR for #356361 (closed), integrating backend and frontend.

This MR adds the following:

  • fetches the Client ID from the self-managed instance.
  • Uses the user's self-managed URL for API requests.

To best understand what's happening here, it's recommended to watch the demo video: https://youtu.be/7SvBNCVdyN4

TODO:

  • frontend specs

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

🎥 Video run-through: https://youtu.be/7SvBNCVdyN4

In Gitpod:

  1. Start a Gitpod from this MR.
  2. Enable the jira_connect_oauth and jira_connect_oauth_self_managed feature flags.

In your Gitpod's GitLab:

  1. Create a GitLab application (at the admin level) https://docs.gitlab.com/ee/development/integrations/jira_connect.html#test-the-gitlab-oauth-authentication-flow
  2. Set the GitLab for Jira application ID.

In your Jira app:

  1. Select Self Managed
  2. Enter your Gitpod base URL (but this can be any GitLab instance that has the GitLab for Jira application ID set).
  3. Sign in.
  4. Test adding a namespace.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #356361 (closed)

Edited by Justin Ho Tuan Duong

Merge request reports