• Install the GitLab for Jira Cloud app
• Update the GitLab for Jira Cloud app
• Set up OAuth authentication
• Connect the GitLab for Jira Cloud app for self-managed instances
  • Set up your instance
  • Link your instance
• Install the GitLab for Jira Cloud app manually
  • Set up your Jira app
    • Install the application in development mode
    • Create a Marketplace listing
• Configure your GitLab instance to serve as a proxy for the GitLab for Jira Cloud app
• Troubleshooting
  • Browser displays a sign-in message when already signed in
  • Manual installation fails
  • Data sync fails with Invalid JWT error
• Security considerations
• Access to GitLab through OAuth
• Access to Jira through access token

GitLab for Jira Cloud app

You can integrate GitLab and Jira Cloud using the GitLab for Jira Cloud app in the Atlassian Marketplace.

Only Jira users with administrator access can install or configure the GitLab for Jira Cloud app.

Install the GitLab for Jira Cloud app

If you use GitLab.com and Jira Cloud, you can install the GitLab for Jira Cloud app. If you do not use both of these environments, use the Jira DVCS Connector or install the GitLab for Jira Cloud app manually. We recommend the GitLab for Jira Cloud app, because data is synchronized in real time. The DVCS connector updates data only once per hour.

To configure the GitLab for Jira Cloud app, you must have at least the Maintainer role in the GitLab.com namespace.

This integration method supports Smart Commits.

For an overview, see Configure the GitLab for Jira Cloud app from the Atlassian Marketplace.

To install the GitLab for Jira Cloud app:

1. In Jira, go to Jira Settings > Apps > Find new apps, then search for GitLab.

2. Select GitLab for Jira Cloud, then select Get it now, or go to the App in the marketplace directly.

   

3. After installing, to go to the configurations page, select Get started. This page is always available under Jira Settings > Apps > Manage apps.

   

4. To add namespaces, ensure you’re signed in to GitLab.com as a user with at least the Maintainer role.

   

5. To open the list of available namespaces, select Add namespace.

6. Identify the namespace you want to link, and select Link.
   • You must have at least the Maintainer role for the namespace.
   • Only Jira site administrators can add or remove namespaces for an installation.

   

After a namespace is added:

• All future commits, branches, and merge requests of all projects under that namespace are synced to Jira.
• From GitLab 13.8, past merge request data is synced to Jira.

Support for syncing past branch and commit data is tracked in this issue.

Update the GitLab for Jira Cloud app

Most updates to the app are fully automated and don’t require any user interaction. See the Atlassian Marketplace documentation for details.

If the app requires additional permissions, the update must first be manually approved in Jira.

Set up OAuth authentication

The GitLab for Jira Cloud app is switching to OAuth authentication. To enable OAuth authentication, you must create an OAuth application on the GitLab instance.

Enabling OAuth authentication is:

• Required to connect the GitLab for Jira Cloud app for self-managed instances.
• Recommended to install the GitLab for Jira Cloud app manually.

To create an OAuth application:

1. On the top bar, select Main menu > Admin.
2. On the left sidebar, select Applications (/admin/applications).
3. Select New application.
4. In Redirect URI:
   • If you’re installing the app from the official marketplace listing, enter https://gitlab.com/-/jira_connect/oauth_callbacks.
   • If you’re installing the app manually, enter <instance_url>/-/jira_connect/oauth_callbacks and replace <instance_url> with the URL of your instance.
5. Clear the Trusted and Confidential checkboxes.
6. In Scopes, select the api checkbox only.
7. Select Save application.
8. Copy the Application ID value.
9. On the left sidebar, select Settings > General (/admin/application_settings/general).
10. Expand the GitLab for Jira App section.
11. Paste the Application ID value into Jira Connect Application ID.
12. Select Save changes.
13. Optional. Enable the jira_connect_oauth feature flag to avoid authentication problems in some browsers.

Connect the GitLab for Jira Cloud app for self-managed instances

Prerequisites:

• GitLab.com must serve as a proxy for the instance.
• The instance must be publicly available.
• The instance must be on version 15.7 or later.

You can link self-managed instances after installing the GitLab for Jira Cloud app from the marketplace. Jira apps can only link to one URL per marketplace listing. The official listing links to GitLab.com.

If your instance doesn’t meet the prerequisites or you don’t want to use the official marketplace listing, you can install the app manually.

It’s not possible to create branches from Jira for self-managed instances. For more information, see issue 391432.

Set up your instance

To set up your self-managed instance for the GitLab for Jira Cloud app in GitLab 15.7 and later:

1. Set up OAuth authentication.
2. On the top bar, select Main menu > Admin.
3. On the left sidebar, select Settings > General (/admin/application_settings/general).
4. Expand the GitLab for Jira App section.
5. In Jira Connect Proxy URL, enter https://gitlab.com.
6. Select Save changes.

Link your instance

To link your self-managed instance to the GitLab for Jira Cloud app:

1. Install the GitLab for Jira Cloud app.
2. Select GitLab (self-managed).
3. Enter your GitLab instance URL.
4. Select Save.

Install the GitLab for Jira Cloud app manually

If your GitLab instance is self-managed and you don’t want to use the official marketplace listing, you can install the app manually.

Prerequisites:

• The instance must be publicly available.
• You must set up OAuth authentication.

Set up your Jira app

Each Jira Cloud application must be installed from a single location. Jira fetches a manifest file from the location you provide. The manifest file describes the application to the system. To support self-managed GitLab instances with Jira Cloud, you can do one of the following:

• Install the application in development mode.
• Create a Marketplace listing.

Install the application in development mode

You can configure your Atlassian Cloud instance to allow you to install applications from outside the Marketplace, which allows you to install the application:

1. Sign in to your Jira instance as an administrator.
2. Place your Jira instance into development mode.
3. Sign in to your GitLab application as a user with administrator access.
4. Install the GitLab application from your Jira instance, as described in the Atlassian developer guides:

   1. In your Jira instance, go to Apps > Manage Apps and select Upload app:

      

   2. For App descriptor URL, provide the full URL to your manifest file, based on your instance configuration. By default, your manifest file is located at /-/jira_connect/app_descriptor.json. For example, if your GitLab self-managed instance domain is app.pet-store.cloud, your manifest file is located at https://app.pet-store.cloud/-/jira_connect/app_descriptor.json.
   3. Select Upload. Jira fetches the content of your app_descriptor file and installs it.

   4. If the upload is successful, Jira displays a modal panel: Installed and ready to go! To configure the integration, select Get started.

      

5. Disable development mode on your Jira instance.

The GitLab for Jira Cloud app now displays under Manage apps. You can also select Get started to open the configuration page rendered from your GitLab instance.

Create a Marketplace listing

If you prefer to not use development mode on your Jira instance, you can create your own Marketplace listing for your instance. This enables your application to be installed from the Atlassian Marketplace.

For full instructions, review the Atlassian guide to creating a marketplace listing. To create a Marketplace listing:

1. Register as a Marketplace vendor.
2. List your application using the application descriptor URL.
   • Your manifest file is located at: https://your.domain/your-path/-/jira_connect/app_descriptor.json
   • We recommend you list your application as private, because public applications can be viewed and installed by any user.
3. Generate test license tokens for your application.

Configure your GitLab instance to serve as a proxy for the GitLab for Jira Cloud app

A GitLab instance can serve as a proxy for other GitLab instances using the GitLab for Jira Cloud app. This can be useful if you are managing multiple GitLab instance but only want to manually install the GitLab for Jira app once.

To configure your GitLab instance to serve as a proxy:

1. On the top bar, select Main menu > Admin.
2. On the left sidebar, select Settings > General (/admin/application_settings/general).
3. Expand the GitLab for Jira App section.
4. Select Enable public key storage.
5. Select Save changes.
6. Install the GitLab for Jira Cloud app manually

Other GitLab instances using the proxy must configure the Jira Connect Proxy URL setting and the OAuth application Redirect URI to point to the proxy instance.

Troubleshooting

Browser displays a sign-in message when already signed in

You might get the following message prompting you to sign in to GitLab.com when you’re already signed in:

You need to sign in or sign up before continuing.

The GitLab for Jira Cloud app uses an iframe to add namespaces on the settings page. Some browsers block cross-site cookies, which can lead to this issue.

To resolve this issue, set up OAuth authentication and enable the jira_connect_oauth feature flag.

Manual installation fails

You might get an error if you have installed the GitLab for Jira Cloud app from the official marketplace listing and replaced it with manual installation. To resolve this issue, disable the Jira Connect Proxy URL setting.

• In GitLab 15.7:

  1. Open a Rails console.
  2. Execute ApplicationSetting.current_without_cache.update(jira_connect_proxy_url: nil).

• In GitLab 15.8 and later:

  1. On the top bar, select Main menu > Admin.
  2. On the left sidebar, select Settings > General (/admin/application_settings/general).
  3. Expand the GitLab for Jira App section.
  4. Clear the Jira Connect Proxy URL text box.
  5. Select Save changes.

Data sync fails with Invalid JWT error

If the GitLab for Jira Cloud app continuously fails to sync data, it may be due to an outdated secret token. Atlassian can send new secret tokens that must be processed and stored by GitLab. If GitLab fails to store the token or misses the new token request, an Invalid JWT error occurs.

To resolve this issue on GitLab self-managed, follow one of the solutions below, depending on your app installation method.

• If you installed the app from the official marketplace listing:

  1. Open the GitLab for Jira Cloud app on Jira.
  2. Select Change GitLab version.
  3. Select GitLab.com (SaaS).
  4. Select Change GitLab version again.
  5. Select GitLab (self-managed).
  6. Enter your GitLab instance URL.
  7. Select Save.

• If you installed the GitLab for Jira Cloud app manually:

  • In GitLab 14.9 and later:
    • Contact the Jira Software Cloud support and ask to trigger a new installed lifecycle event for the GitLab for Jira Cloud app in your namespace.
  • In all GitLab versions:
    • Re-install the GitLab for Jira Cloud app. This might remove all already synced development panel data.

Security considerations

The GitLab for Jira Cloud app connects GitLab and Jira, as data must be shared between the two applications and access must be granted in both directions.

Access to GitLab through OAuth

GitLab does not share an access token with Jira. However, users must authenticate via OAuth to configure the app.

An access token is retrieved via PKCE OAuth flow, and stored only on the client side. The app-frontend that initializes the OAuth flow is a JavaScript application, which is loaded from GitLab through an iframe on Jira.

The OAuth application requires the api scope that grants complete read/write access to the API, including to all groups and projects, the container registry, and the package registry. However, the GitLab for Jira Cloud app only uses this access to:

• Display namespaces to be linked.
• Link namespaces.

Access through OAuth is only needed for the time a user configures the GitLab for Jira Cloud app. For more information, see Access token expiration.

Access to Jira through access token

Jira shares an access token with GitLab to authenticate and authorize data pushes to Jira. As part of the app installation process, Jira sends a handshake request to GitLab containing the access token. The handshake is signed with an asymmetric JWT and the access token is stored encrypted with AES256-GCM on GitLab.