Allure TestOps plugin for Jira issue tracker
This article covers the usage of Allure TestOps plugins for Jira with Allure TestOps releases 4+ only.

Jira plugins

At the moment there are two Allure TestOps plugins for Jira issue tracker:

  1. Allure TestOps plugin for Jira server / Jira DC
  2. Allure TestOps plugin for Jira Cloud.

these two have different installation paths (two different systems, huh) but the configuration approach is pretty much the same.

Prerequisites

You need to have a ready to use integration with your Jira instance:

  1. Integration with an instance of Jira issue tracker is to be added globally

    1. URL of the instance is to be provided

    if you see this text, report to help.qameta.io

  2. Integration is to be added on a project level with real credentials.

    if you see this text, report to help.qameta.io

    if you see this text, report to help.qameta.io

  3. Allure TestOps plugin for your Jira type is added to your instance from Atlassian market.

  4. If your Jira instance uses https for the access to Jira UI, then you must use secure cookies on Allure Test side.

    1. Check your configuration parameters at gateway service
    2. Locate the parameters responsible for secure cookies
      1. ALLURE_SECURE_COOKIE in .env file of docker compose deployment
      2. secureCookies for Helm chart’s values.yaml
      3. ALLURE_SECURE in gateway configuration file of packages deployment
  5. To use this integration you need to have enabled account on Allure TestOps side.

    • The account can be with any authority level (ADMIN, USER, AUDITOR).
  6. Your browser must allow usage of 3rd party cookies.

Configuration of Allure TestOps plugin

You need to have either Jira administrator privileges or a Jira administrator close to you to configure Allure TestOps plugin for Jira.

Find the plugin

  1. Click gear icon in the upper right corner.
  2. Select manage apps
  3. Find Allure TestOps plug-in
  4. Click Configure

Configure the plug-in

if you see this text, report to help.qameta.io

  1. Select new config
  2. Add your Allure TestOps URL, e.g. https://allure.testops.xyz (of course you need to add a real one)
  3. Release of Allure TestOps is to be 4
  4. The integration ID is the system ID of the integration you added on the global level (under Administration section).
    • The required ID always stands before the integration’s name.
  5. If you want to limit the usage of plugin by specific Jira’s groups, then check appropriate check-box.
  6. Select the groups allowed to use Allure TestOps plugin. The rest of the groups won’t see Allure TestOps plugin’s elements on Jira issues pages.
  7. If you want to limit the usage of plugin by specific projects, then check appropriate check-box.
  8. Select the projects where you need to see the data from Allure TestOps.
  9. Save the settings.

Config will be saved with the name of Allure TestOps server URL.

Troubleshooting

Normal work

If all the settings are correct, you will see the following in your Jira issues.

Connection works, there are no test cases and/or launches linked to an issue

In case all is fine, but no there are no test cases and/or launches linked to current issue, you’ll see the notification from Allure TestOps server No test cases for linked test cases section, and No launches for the launches section.

if you see this text, report to help.qameta.io

Connection works, there are test cases and/or launches linked to an issue

In case all is fine, and there are test cases and/or launches linked to current issue, you’ll see the list of those:

if you see this text, report to help.qameta.io

Action is required

Connection works, current user is not logged in to Allure TestOps - green Login buttons

if you see this text, report to help.qameta.io

If current user is not logged in to Allure TestOps, then the plugin will show fresh green Login button(s). You have a very difficult task — you need to decide which one you want to click.

After the decision and action are made, you will be redirected to Allure TestOps instance login page, where you need to login using your existing credentials.

Then you need to go back to Jira and refresh the page.

Allure TestOps Configuration is required

Connection works, current user is logged in to Allure TestOps - green Login buttons do not disappear

if you see this text, report to help.qameta.io

If current user is logged in to Allure TestOps and the plugin still shows fresh green Login button(s), this could mean you haven’t fulfilled the item #4 of the prerequisites.

Please go back to the prerequisites, check item #4 and configure Allure TestOps as described.

Browser settings alteration is required

Connection works, current user is logged in to Allure TestOps - green Login buttons do not disappear

If previous solution (ALLURE_SECURE) still does not affect the behaviour, it’s time to check your browser settings.

if you see this text, report to help.qameta.io

If current user is logged in to Allure TestOps and the plugin sill shows fresh green Login button(s), and the configuration contains all needed ALLURE_SECURE stuff, this could mean your browser does not allow the usage of 3rd party cookies (these are required the integration to work).

Safari settings

You need to uncheck the following parameter:

if you see this text, report to help.qameta.io

Google Chrome

In Google Chrome and generally in all Chromium based browsers the following needs to be allowed for the integration to work properly.

if you see this text, report to help.qameta.io

FireFox

In Google Chrome and generally in all Chromium based browsers the following needs to be allowed for the integration to work properly.

if you see this text, report to help.qameta.io

Infrastructure troubleshooting is required

If you see the following or similar with an error where is is not expected, we have the worst case then

if you see this text, report to help.qameta.io

Infrastructure issues troubleshooting

When we’re talking about the infrastructure there are usually 3 places to check:

  1. Allure TestOps environment (firewalls, reverse proxies and other network elements processing the traffic)
  2. Network (generally traffic between the Allure TestOps infrastructure and Jira infrastructure could be blocked)
  3. Jira environment (firewalls, reverse proxies and other network elements processing the traffic)

if you see this text, report to help.qameta.io

Trying to identify the faulty party - direct connection

All the information you see in the jira plug-in is actually an iframe generated on Allure TestOps side, so if we exclude items 2 and 3 and check if you can access the iframe content directly and there are no errors in Allure TestOps:

  1. Open developer tools of your browser.

  2. Locale one of the elements related to Allure TestOps content

  3. Locate the element on the page

    if you see this text, report to help.qameta.io

  4. Copy the src data of the iframe, so the string you have will look like follows:

    • https://your-allure-testops-instance/iframe/issue-tracker-testcases?integrationId=5&issueKey=AE-1
    • AE-1 is the ID of jira issue, it’ll be specific to your settings
    • integrationId=5 has to be the correct reference to the integration ID configures at Allure TestOps side.
  5. Paste the copied string to browser’s address bar. Check what your browser shows.

What your browser shows
  1. If you see a message saying there are no test cases or no launches or yo u see a list oof test cases or launches related to this Jira issue, then settings are correct on Allure TestOps side.

Good:

if you see this text, report to help.qameta.io

Also good:

if you see this text, report to help.qameta.io

If you still see sad face or an error message, you first need to check you’ve provided correct integration ID (integration must exist and it has to be an issue tracker).

If Issue tracker ID is correct, you need to check the network rules and make sure the connections to Allure TestOps are allowed.

If direct connection works

Here all the fun starts. You need to engage a network admin or a DevOps or whoever is responsible for the network and infrastructure on Jira side.

You need to check if the communication between Jira and Allure TestOps is allowed.

What if we have Jira Cloud?

In this case the infrastructure, network rules, white and black lists of IP addresses or FQDNs or even whole 2nd level domains are managed by Atlassian company and you need to file a tech support request to Atlassian.

We have experience with some cases when whole 2nd level domains (.tech for example) were blocked by Atlassian with no explanaion.