Jira Data Center

Jira Data Center is the self-hosted Jira integration for Allure TestOps. It covers:

• linking test cases, launches, results, and defects to Jira issues;
• configuring issue mappings so test metadata becomes Jira links in Allure TestOps;
• embedding Allure TestOps panels inside Jira Data Center issues through the Jira app;
• synchronizing defect lifecycle state through Jira webhooks.

The embedded panels run in an iFrame. The Allure TestOps instance does not need to be reachable from the Jira server, but it must be reachable from the user's browser. Browser settings that block cross-site cookies can prevent the panels from loading. If users report issues, see Troubleshooting.

For manual issue lookup from Allure TestOps, the Allure TestOps server must be able to reach the Jira instance.

Before you begin

• The Jira Data Center URL.
• Either a Jira personal access token or a Jira username and password.
• Instance administrator access in Allure TestOps.
• Project owner access in the target Allure TestOps project.
• Jira administrator access if you want the embedded panels or webhook sync.
• HTTPS enabled on both Allure TestOps and Jira if you want the embedded panels to work. A mixed HTTP/HTTPS setup is not supported for the iFrame path.

1. Enable Jira issue links in Allure TestOps

Create the Jira credentials

You can authenticate Allure TestOps against Jira with either a personal access token or a username and password. To use a token:

1. In Jira, click your avatar and go to Profile.
2. In the left sidebar, go to Personal access tokens.
3. Click Create token.
4. Fill in the fields:
   • Token Name: a name to identify the token, for example Token for Allure TestOps.
   • Expiry date: when the token expires. After this date the integration will stop working. To create a token with no expiration, clear the Automatic expiry checkbox.
5. Click Create and copy the token. Save it in a secure location.

Add the global Jira integration

An instance administrator should:

1. Open Administration → Integrations in Allure TestOps.
2. Click + Add integration.
3. Select Jira Server (DC).
4. Fill in the fields:
   • Name: a stable name for the Jira instance, for example Jira production.
   • Endpoint: the URL of the Jira Data Center instance, for example https://jira.example.com.
5. If Jira uses a self-signed certificate, disable certificate validation.
6. Click Add integration.

Enable the integration in the project

• From administration panel
• From project settings

1. Go to Administration → Integrations.
2. Find and open your Jira Data Center integration.
3. Go to the Projects tab.
4. Click + next to the search field.
5. Select the target Allure TestOps project.
6. Enter credentials:
   • basic tab: Jira username and password;
   • token tab: the personal access token created above.
7. Click Test connection. If the credentials are correct, a "Connection established" message appears.
8. Click Add integration.

1. In Allure TestOps, open the target project.
2. Go to Settings → Integrations.
3. Under Available integrations, find the Jira Data Center integration and click Add integration.
4. Enter credentials:
   • basic tab: Jira username and password;
   • token tab: the personal access token created above.
5. Click Test connection. If the credentials are correct, a "Connection established" message appears.
6. Save the project integration.

Configure issue mapping

If your tests already emit issue labels through an Allure adapter, configure an issue mapping so Allure TestOps can turn those labels into Jira links automatically.

1. Open the Allure TestOps project.
2. Go to Settings → Issues.
3. Click + Create.
4. Fill in the fields:
   • Key: the short identifier your tests use in metadata, for example jira.
   • Issue tracker: the Jira Data Center integration enabled for the project.
5. Save the issue mapping.

To emit issue labels from your tests, use the Allure adapter for your framework. Example in TypeScript:

allure.label("jira", "BUG-123");

Here jira is the mapping key and BUG-123 is the Jira issue ID. In a real project, wrap the label call in a helper function so the key is defined in one place.

2. Embed Allure TestOps panels in Jira Data Center issues

The embedded panels show linked Allure TestOps test cases and launches directly inside Jira issues, not individual test results, see Issues. This requires secure cookies, the Jira app, and the Allure TestOps integration ID.

Enable secure cookies in Allure TestOps

• Kubernetes
• Docker Compose
• DEB
• RPM

Set network.tls.secureCookie to true in values.yaml.

Set TESTOPS_SECURE_COOKIE=true in .env, then restart Allure TestOps.

Set ALLURE_SECURE=true in /opt/testops/conf/testops.conf, then restart Allure TestOps.

Set ALLURE_SECURE=true in /opt/testops/conf/testops.conf, then restart Allure TestOps.

Find the integration ID in Allure TestOps

• From administration panel
• From project settings

1. Go to Administration → Integrations.
2. Find your Jira Data Center integration.
3. Copy the ID displayed to the left of the integration name.

1. In Allure TestOps, open the target project.
2. Go to Settings → Integrations.
3. Under Added integrations, find your Jira Data Center integration.
4. Copy the ID displayed to the left of the integration name.

Install and configure the Jira app

1. In Jira, click the Settings icon and select Manage apps.

2. Find Allure TestOps for JIRA and click Install.

3. After installation, go to Manage apps in the left sidebar.

4. Expand the Allure TestOps for JIRA section and click Configure.

5. Fill in the fields:

   • Config: select Create new config if this is the first Allure TestOps instance you connect from Jira; otherwise select the existing instance URL to update its settings.
   • Endpoint: the Allure TestOps URL without a trailing slash.
   • Version: the option that matches your current Allure TestOps release line.
   • Integration ID: the Jira Data Center integration ID from the step above.
   • Selected groups / Groups: Jira groups that should see the plugin panels. Leave unchecked to enable for all groups.
   • Selected projects / Projects: Jira projects where panels should appear. Leave unchecked for all projects.
   • Selected issue types / Issue types: issue types where panels should appear. Leave unchecked for all types.

6. Click Save.

Verify the integration

1. In Allure TestOps, add a Jira issue link to a test case or launch.

   

2. Confirm that the Jira issue picker can search the expected project.

3. Open the linked Jira issue and confirm that the Allure TestOps panels appear.

   

3. Enable synchronization of the issue lifecycles

When this path is enabled, Jira issue status changes can open or close the linked defect in Allure TestOps.

Create the webhook in Allure TestOps

1. Open Administration → Integrations in Allure TestOps.
2. Open the Jira Data Center integration.
3. Go to the Webhooks tab.
4. Click + Create webhook and confirm the creation.
5. Copy the generated webhook URL.

Add the webhook in Jira

1. In Jira, click the Settings icon and select System.
2. In the left sidebar, under Advanced, click WebHooks.
3. Click Create a WebHook.
4. Fill in the fields:
   • Name: a name to identify the webhook.
   • Status: Enabled.
   • URL: the webhook URL copied from Allure TestOps.
   • Issue related events: select Issue → updated.
5. Click Create.

Troubleshooting

The defect is not closed when the Jira issue is closed

Allure TestOps closes the linked defect when the Jira issue gets a Resolution. If the issue moves to a final status but its Resolution field stays empty, the defect stays open.

Check that:

• the webhook from step 3 is enabled and sends Issue → updated events;
• the Jira workflow sets Resolution on the transition to the final status, for example with a transition screen or a post function.

The iFrame shows a sign-in button

The panels show Allure TestOps data only to users who are signed in to Allure TestOps and have access to the project. For users who only need to view the data, you can create Guest accounts, see Manage guests.

On a self-hosted instance, check that secure cookies are enabled. In the browser developer tools, open Application → Cookies for the Allure TestOps address and find the ALLURE_TESTOPS_SESSION cookie. It must have Secure set and SameSite equal to None. If it does not, enable secure cookies as described in Enable secure cookies in Allure TestOps, then sign out of Allure TestOps and sign in again.

If you are signed in to Allure TestOps but still see a Sign in button in the Jira issue view, the browser is blocking the cross-site cookies required for the embedded panel.

• Google Chrome
• Mozilla Firefox
• Apple Safari

1. Go to Settings → Privacy and security → Third-party cookies.
2. Select Allow third-party cookies.

1. Go to Settings → Privacy & Security.
2. Under Enhanced Tracking Protection, select Custom.
3. Check Cookies and set the dropdown to Cross-site tracking cookies.

1. Go to Safari → Settings → Privacy.
2. Clear the Prevent cross-site tracking checkbox.

Each user who encounters this issue needs to apply the fix in their own browser.

The iFrame shows no content

An empty iFrame panel usually means Jira is running on HTTPS and Allure TestOps is running on HTTP. This configuration is not supported. Enable HTTPS for Allure TestOps and update the Endpoint field in the Jira plugin configuration from http to https.

The iFrame shows "Couldn't connect to Allure TestOps"

The integration ID in the Jira plugin configuration is incorrect. Find the correct integration ID in Allure TestOps and update the value in the plugin settings.

Related pages

• Jira Software Cloud for the Atlassian-cloud integration path.
• Defects for issue-linked defect workflows.
• Links, issues, and relations for how issue links appear in Allure TestOps.