Set up a Jira development environment
The following are required to install and test the app:
-
A Jira Cloud instance. Atlassian provides free instances for development and testing.
-
A GitLab instance available over the internet. For the app to work, Jira Cloud should be able to connect to the GitLab instance through the internet. For this we recommend using Gitpod or a similar cloud development environment. For more information on using Gitpod with GDK, see the:
- GDK in Gitpod video.
- GDK with Gitpod documentation.
You must not use tunneling tools such as Serveo or
ngrok
. These are security risks, and must not be run on developer laptops.Jira requires all connections to the app host to be over SSL. If you set up your own environment, remember to enable SSL and an appropriate certificate.
Install the app in Jira
To install the app in Jira:
-
Enable Jira development mode to install apps that are not from the Atlassian Marketplace:
- In Jira, navigate to Jira settings > Apps > Manage apps.
- Scroll to the bottom of the Manage apps page and select Settings.
- Select Enable development mode and select Apply.
-
Install the app:
-
In Jira, navigate to Jira settings > Apps > Manage apps.
-
Select Upload app.
-
In the From this URL field, provide a link to the app descriptor. The host and port must point to your GitLab instance.
For example:
https://xxxx.gitpod.io/-/jira_connect/app_descriptor.json
-
Select Upload.
If the install was successful, you should see the GitLab for Jira Cloud app under Manage apps. You can also select Getting Started to open the configuration page rendered from your GitLab instance.
Note that any changes to the app descriptor requires you to uninstall then reinstall the app.
-
Simple setup
To avoid external dependencies like Gitpod and a Jira Cloud instance, use the Jira connect test tool and your local GDK:
-
Clone the Jira-connect-test-tool
git clone git@gitlab.com:gitlab-org/manage/integrations/jira-connect-test-tool.git
. -
Start the app
bundle exec rackup
. (The app requires your GDK GitLab to be available onhttp://127.0.0.1:3000
.). -
Open
config/gitlab.yml
and uncomment thejira_connect
config. -
If running GDK on a domain other than
localhost
, you must add the domain toadditional_iframe_ancestors
. For example:additional_iframe_ancestors: ['localhost:*', '127.0.0.1:*', 'gdk.test:*']
-
Restart GDK.
-
Go to
http://127.0.0.1:3000/-/profile/personal_access_tokens
. -
Create a new token with the
api
scope and copy the token. -
Go to
http://localhost:9292
. -
Paste the token and select Install GitLab.com Jira Cloud app.
Test the GitLab OAuth authentication flow
- Introduced in GitLab 14.9 with a flag named
jira_connect_oauth
. Disabled by default.- Generally available in GitLab 16.0. Feature flag
jira_connect_oauth
removed.
GitLab for Jira users can authenticate with GitLab using GitLab OAuth.
The following steps describe setting up an environment to test the GitLab OAuth flow:
- Start a Gitpod session.
- On your GitLab instance, go to Admin > Applications.
- Create a new application with the following settings:
- Name:
GitLab for Jira
- Redirect URI:
YOUR_GITPOD_INSTANCE/-/jira_connect/oauth_callbacks
- Trusted: No
- Confidential: No
- Scopes:
api
- Name:
- Copy the Application ID value.
- Go to Admin > Settings > General.
- Expand GitLab for Jira App.
- Paste the Application ID value into Jira Connect Application ID.
- In Jira Connect Proxy URL, enter
YOUR_GITPOD_INSTANCE
(for example,https://xxxx.gitpod.io
). - Select Enable public key storage.
- Select Save changes.
Troubleshooting
App installation fails
If the app installation fails, you might need to delete jira_connect_installations
from your database.
- Open the database console.
- Run
TRUNCATE TABLE jira_connect_installations CASCADE;
.
Not authorized to access the file
If you use Gitpod and you get an error about Jira not being able to access the descriptor file, you might need to make the GDK port public by following these steps:
- Open your GitLab workspace in Gitpod.
- When the GDK is running, select Ports in the bottom-right corner.
- On the left sidebar, select the port the GDK is listening to (typically
3000
). - If the port is marked as private, select the lock icon to make it public.