TestOps logo
Try TestOps

Jira Software Cloud

Jira service accounts are not supported. The integration must be configured using a regular user account.

Jira Software Cloud (JSC) is the cloud-hosted Jira Software application that can be integrated with Allure TestOps. The integration of Allure TestOps and JSC covers the following.

  • 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 Cloud 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 Jira Cloud, but it must be reachable from the user's browser. Browser settings that block cross-site cookies can prevent the panels from loading — see Troubleshooting if users report issues.

For the issues lookup from Allure TestOps, the Allure TestOps server must be able to reach Jira Software Cloud API endpoints.

Before you begin

You need to have

  • A JSC site, for example https://company.atlassian.net.
  • Access to create an Atlassian API token.
  • 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.
  • Allure TestOps to work over HTTPS (behind a reverse proxy etc. to ensure HTTPS traffic) if you want the embedded panels of Allure TestOps plugin for Jira Cloud to work.

Create the JSC API token

  1. In JSC UI click your avatar and go to Profile.
  2. Click Manage your account.
  3. Go to the Security tab.
  4. Under API tokens, click Create and manage API tokens.
  5. Click Create API token.
  6. Enter a name to identify the token, for example Token for Allure TestOps.
  7. Click Create, then click Copy to copy the token. Save it in a secure location to apply in the next steps.

Add the global Jira integration in Allure TestOps

An instance administrator needs to perform the following:

  1. Open Administration → Integrations in Allure TestOps.
  2. Click + Add integration.
  3. Select Jira Software Cloud.
  4. Fill in the fields:
    • Name — a stable name for the Jira instance, for example company.atlassian.net.
    • Endpoint — the Jira site URL, for example https://company.atlassian.net.
  5. Click Add integration.

Add the JSC integration to the project

  1. Go to Administration → Integrations.
  2. Find and open your Jira Software Cloud integration.
  3. Go to the Projects tab.
  4. Click + next to the search field.
  5. Select the target Allure TestOps project.
  6. Fill in the fields:
    • Username — the email address used to sign in to Jira Software Cloud.
    • API token — the 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 Software Cloud integration and click Add integration.
  4. Fill in the fields:
    • Username — the email address used to sign in to Jira Software Cloud.
    • API token — the 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 produce issue labels through an Allure Framework adapter, configure an issue mapping so Allure TestOps can turn those labels into Jira links.

  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 Software Cloud integration you have enabled in previous steps for the project.
  5. Save the issue mapping.

Issue mapping configuration in Allure TestOps

To emit issue labels from your tests, use the Allure adapter for your framework. Here jira is the mapping key and AE-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.

Examples

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

import allure
from allure_commons.types import LabelType

@allure.label("jira", "AE-123")
def test_authentication():
   pass

Allure.label("jira", "AE-123");

For more examples see the Reference chapter of the documentation for your favourite test framework. in the section Label.

2. Embed Allure TestOps panels in Jira Cloud issues

The embedded panels show linked Allure TestOps test cases and launches directly inside JSC issues. The setup depends on your Allure TestOps deployment:

  • Allure TestOps Cloud: configure the Jira Cloud app and specify the Allure TestOps URL and integration ID. No additional server-side secure cookie configuration is required.
  • Self-hosted Allure TestOps: configure secure cookies (see the section below) for your deployment method, then configure the Jira Cloud app.

Both setups require the Jira integration ID. Allure TestOps must be accessible from the user's browser over HTTPS.

Enable secure cookies in Allure TestOps

This section applies only to self-hosted Allure TestOps instances. If you use Allure TestOps Cloud, skip this section and proceed to Find the integration ID in Allure TestOps.

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

  1. Go to Administration → Integrations.
  2. Find your Jira Software Cloud 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 Software Cloud integration.
  4. Copy the ID displayed to the left of the integration name.

Integration ID location in Allure TestOps

Install and configure the plugin Allure TestOps for Jira Cloud

Install and configure Allure TestOps for Jira Cloud.

  1. Open the Allure TestOps for Jira Cloud page in the Atlassian Marketplace.
  2. Click Get it now and complete the installation for your Jira site.
  3. After installation, open the app configuration as described in the next tab.
  1. Open Jira administration and go to Connected apps.
  2. Find Allure TestOps for Jira Cloud.
  3. Click the three-dot menu (⋯) to the right of Manage app.
  4. Select Configure app.

In the app configuration, fill in the following fields:

  • Allure TestOps URL — the HTTPS URL of your Allure TestOps instance.
  • Integration ID — the numeric ID of your Jira Software Cloud integration in Allure TestOps.
  • Allowed projects — select the Jira projects where the Allure TestOps panels should appear. Leave this field empty to allow all projects.
  • Allowed issue types — select the Jira issue types where the Allure TestOps panels should appear. Leave this field empty to allow all issue types.

Click Save.

If you are using on-prem deployment of Allure TestOps, then you will be asked to approve custom endpoint (the address of API endpoints of the deployed Allure TestOps) for the plugin. You need to approve the custom endpoint, otherwise Allure TestOps panels won't render any information from Allure TestOps.

Open the Allure TestOps for Jira Cloud plugin configuration

Enable Allure TestOps panels in Jira issues

After configuring the app, choose which Allure TestOps panels to display in Jira issues.

  1. Open a Jira issue.
  2. Click the gear icon in the upper-left area of the issue interface.
  3. Select the Allure TestOps panels to display:
    • Allure TestOps: Test Cases
    • Allure TestOps: Launches
  4. Apply or save the selection if prompted.
  5. Reload the Jira issue and check that the selected panels appear.

The panels display Allure TestOps information linked to the Jira issue. Make sure the relevant test cases or launches are linked to the issue in Allure TestOps.

Verify the integration

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

    Jira issue links in an Allure TestOps test result

  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.

    Allure TestOps panels embedded in a Jira Cloud issue

3. Enable synchronization of the defects lifecycle with linked issue

When this path is enabled, Jira issue status changes can affect (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 Software Cloud 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 only Issue → updated.
  5. Click Create.

Troubleshooting

The Allure TestOps panels show the sign-in button

iFrame showing the sign-in button instead of Allure TestOps content

If you have just enabled Secure cookies for your on-premise deployment, then log out from Allure TestOps, then login again and check if Allure TestOps panels still showing the login button.

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

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

Allow third-party cookies option in Chrome settings

  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.

Cross-site tracking cookies option in Firefox settings

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

Prevent cross-site tracking option in Safari settings

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

The Allure TestOps panels show "Couldn't connect to Allure TestOps"

panel is showing the "Couldn't connect to Allure TestOps" message

The integration ID in the Jira app configuration might be incorrect. Find the correct integration ID in Allure TestOps and update the value in the app settings.

The Allure TestOps panels show a connection failure or 502 error

iFrame showing a connection failure icon

If the embedded panels show a connection failure icon or a 502 error instead of Allure TestOps data, first check that the Allure TestOps instance is available and reachable from the browser.

If Allure TestOps is available but the problem persists, the Jira Software Cloud content security policy may be blocking requests from the Allure TestOps domain. To investigate:

  1. In Jira, open an issue where the Allure TestOps content is expected.

  2. Open browser developer tools and use the element inspector to locate the <iframe> that corresponds to the Allure TestOps panel.

  3. Copy the URL from the src attribute of that <iframe>.

    The iFrame src URL in browser dev tools

  4. Contact Atlassian support with the iFrame URL and ask why requests to that domain are being blocked.

The integration stopped working after August 2025

Atlassian deprecated several Jira Software Cloud API endpoints in August–September 2025. If the integration was working before that period and then stopped, the cause is likely that the Allure TestOps version in use relies on those deprecated endpoints.

To restore the integration, upgrade Allure TestOps to version 25.3.1 or later, which adds support for the replacement Atlassian API.

Tips and tricks

Jira Cloud plugin and Allure TestOps that is not exposed to the internet

Working with Jira Software Cloud and an Allure TestOps instance deployed on-premise (not exposed to the internet, e.g. only reachable via LAN) requires some extra configuration.

Here is the diagram

  1. End user is in the corporate network.
  2. Allure TestOps is in the corporate network.
  3. Allure TestOps is not exposed to the internet.
    1. Meaning: there is no direct connection from JSC to Allure TestOps.
    2. All magic happens in the end user's browser.
  4. End user can access both — Allure TestOps and Jira Software Cloud using their browser.

Main requirements

Failing to comply with these requirements will result in a failed integration:

  1. The Allure TestOps for Jira plugin must be installed.
  2. Secure cookies must be enabled.
  3. 3rd party cookies must be allowed.
  4. If using an enterprise (managed) version of a Chromium-based browser, the applied policies must allow connections to LAN resources — see Google's Local Network Access policies.

Chromium enterprise policies for LAN-only Allure TestOps instances

Chromium enforced a change that blocks pages from making requests to LAN resources unless explicitly allowed by policy. This affects the plugin's iframe when Allure TestOps is only reachable on the local network (e.g. no public DNS).

To make it work, the following enterprise policies had to be configured:

  • LocalNetworkAccessAllowedForUrls — takes a list (array) of URLs that are allowed to make requests to LAN resources.
  • LocalNetworkAccessPermissionsPolicyDefaultEnabled — must be set to true. Setting it to false prevents the iframe from loading.

Vivaldi browser

# add https://testopstests.atlassian.net to the list of external URLs that can request content from the local network
defaults write com.vivaldi.Vivaldi LocalNetworkAccessAllowedForUrls -array 'https://yourinstance.atlassian.net'
# delete policy
defaults delete com.vivaldi.Vivaldi LocalNetworkAccessAllowedForUrls

# enable LocalNetworkAccessPermissionsPolicyDefaultEnabled
# this is the main trick
defaults write com.vivaldi.Vivaldi LocalNetworkAccessPermissionsPolicyDefaultEnabled -bool true
defaults delete com.vivaldi.Vivaldi LocalNetworkAccessPermissionsPolicyDefaultEnabled

# Temporary solution – remove all restrictions (will be deprecated by chromium soon)
defaults write com.vivaldi.Vivaldi LocalNetworkAccessRestrictionsTemporaryOptOut -bool true
# delete applied policy
defaults delete /Library/Preferences/com.vivaldi.Vivaldi LocalNetworkAccessRestrictionsTemporaryOptOut

Google Chrome

# add https://testopstests.atlassian.net to the list of external URLs that can request content from the local network
defaults write com.google.Chrome LocalNetworkAccessAllowedForUrls -array 'https://yourinstance.atlassian.net'
# delete policy
defaults delete com.google.Chrome LocalNetworkAccessAllowedForUrls

# enable LocalNetworkAccessPermissionsPolicyDefaultEnabled
# this is the main trick
defaults write com.google.Chrome LocalNetworkAccessPermissionsPolicyDefaultEnabled -bool true
# delete applied policy 
defaults delete com.google.Chrome LocalNetworkAccessPermissionsPolicyDefaultEnabled

# Temporary solution – remove all restrictions (will be deprecated by chromium soon)
defaults write com.google.Chrome LocalNetworkAccessRestrictionsTemporaryOptOut -bool true
# delete applied policy
defaults delete /Library/Preferences/com.google.Chrome LocalNetworkAccessRestrictionsTemporaryOptOut

How to check applied policies

open the url: vivaldi:policy or chrome:policy

::: tip Safari (without managed/enforced policies) is not affected by this restriction and works without any additional configuration. :::

If it is not possible to apply such policies, then the only way to proceed is to have Allure TestOps exposed to the internet, at least the endpoints that are used for rendering of the iframe.

In this case end users must use the same URL that is used to expose the iframe endpoint.

Meaning:

  • On Jira Software Cloud side in the settings of the Allure TestOps plugin you must have: https://testops.company.com, the URL that is exposed to the public internet.
    • Exposed endpoint of the intranet is https://testops.company.com/iframe/*.
  • End users use (even in the local network) must use https://testops.company.com to access Allure TestOps.
  • If DNs will be different, then plugin won’t be able to have correct cookies and user won’t be authenticated in Allure TestOps to render the iframe content.
© Qameta Software Inc. All rights reserved.