This article explains how to connect your mabl workspace to a Jira project so you can create and link issues directly from your mabl workspace. Setup happens in two apps and usually involves two roles:
- mabl workspace owner - creates the "Issue tracker" API key and gets the workspace ID from mabl
- Jira admin - a Jira admin with access to all projects installs the mabl app in Jira and enters the mabl API key and workspace ID
Before you start
To set up the Jira Cloud integration, gather the following information from the mabl app:
- "Issue tracker" API key - created in Settings > APIs in the mabl app. API key access is limited to workspace owners.
- Workspace ID - found in Settings > Workspace in the mabl app
Install the mabl Jira Cloud app
Visit the Atlassian marketplace listing for the mabl Automated Testing for Jira app to set up the integration.
Permissions
Only Jira admins, with access to all projects, can install the mabl Jira Cloud app. A Jira project admin or lower does not have enough permissions to set up the integration.
Configure the app
Once the app is installed, click on the Configure button for the mabl Jira Cloud app from the listing or from Settings > Manage Apps in Jira.
Fill in the fields to complete the configuration:
- Name: give the integration a specific name.
- API key: enter the "Issue Tracker" API key from mabl
- Workspace ID: enter the workspace ID from mabl
- Projects: select the specific Jira projects where your mabl workspace should create and link issues
Click on the + Add integration button to complete the installation.
To confirm that the integration is successfully installed, follow steps outlined in this article to create a Jira issue from the mabl app.
Connecting additional workspaces
If you have multiple workspaces in mabl, you can configure your Jira Cloud instance to connect to additional mabl workspaces by taking the following steps:
- Create a new "Issue tracker" API key in the additional mabl workspace
- Get the workspace ID from the additional mabl workspace
- On the mabl Automated Testing for Jira app page, click on the Configure button. Only a Jira admin can add additional workspaces to the integration.
- Enter the configuration information for the additional workspace: Name, "Issue tracker" API key, workspace ID, and Jira project.
- Click on the + Add integration button.
Removing or reinstalling the app
If you uninstall the mabl app from your Jira Cloud instance, or uninstall and reinstall it, the links between mabl tests and their existing Jira issues may break. If you want a record of those links, you can export the issues as a CSV file from Tests > Issues in the mabl app before removing the integration. After you reinstall and reconfigure the app, relink the affected tests to their Jira issues.
Upgrade from an earlier version of the app
Version 2.x and earlier of the mabl Jira Cloud app run on Atlassian Connect, which Atlassian is retiring. Upgrade to version 4.x by January 31, 2027. After that date, earlier versions stop working, and you can't create or link Jira issues from mabl until you upgrade.
An organization admin or site admin approves the upgrade in Atlassian Administration. Under Apps > Sites, select your site, then Connected apps. The mabl app is listed as mabl: Automated Testing with Jira & Rovo. If it shows an Update label, your site is on an earlier version and needs the upgrade.
Open the app's details. A banner says the app version runs on a platform that will be unsupported soon, and Version shows the current version, such as 2.8.0, marked Outdated. Select Update, review the new permissions, and select Update again.
For the full steps, see Atlassian's article Manage an installed app.
The upgrade changes the app's Jira permissions:
-
Removed:
read:connect-jira,write:connect-jira -
Added:
read:jira-work,write:jira-work,read:jira-user,read:app-user-token,read:app-system-token
Your integration settings, connected workspaces, and linked issues carry over.