Use the mabl integration for Jira to create and link Jira issues with mabl tests. With the Jira integration, you can:
- Attach mabl tests and test results to Jira issues for better traceability.
- Capture comprehensive diagnostic data from mabl test results in Jira issues, including screenshots, DOM snapshot, and network activity
- Review failing or flaky mabl tests associated with Jira issues.
- Build mabl tests from the Jira issues that describe the behavior you want to test.
This article explains how to use the Jira integration, including:
- Create new Jira issues in mabl
- Link mabl tests to existing Jira issues
- Manage Jira issues
- Build tests from Jira issues
For setup instructions, check out the article Jira Cloud setup.
Add a mabl Rovo agent
If Rovo is enabled for your Atlassian Cloud instance, you can also create a custom Rovo agent with mabl skills to accomplish even more, including creating mabl tests, retrieving results, and identifying coverage gaps.
To learn more, check out the article on integrating the mabl MCP with Atlassian Rovo.
How to create new issues
The process for creating Jira issues in mabl starts with the New issue form. You can access the New issue form from the following areas of the mabl app:
- From a test run: On the test output page, click on More actions (...) > Create issue in Jira
- From a test: On the test details page, open the Issues tab and click on the + New issue button.
- On the issues page: Click on **Tests **in the left-hand navigation, select the Issues tab and click on the + New issue button.
Creating an issue from a test run
The new issue form
In the New issue form, enter the following information:
- Issue Tracker: Select the issue tracker for this plugin
- Select "Create new"
- Project: Select the Jira project where you want to create the issue
- Type: Select the type of issue you want to create
The New issue form
Click on the Next button and fill out the required fields to create the new Jira issue. For failed tests, mabl automatically pre-fills the summary and description with relevant information from the failure analysis.
Creating a new Jira issue in mabl
Unsupported field
The "linked issues" field is not supported by the Jira integrations. If you want to link an issue, you can link it from within Jira after creating the issue.
Click on the Submit button to create the issue. A success message appears at the bottom of the screen in the mabl app. Click on the link to go directly to the Jira issue in a new tab.
Issues created from a test run include the following diagnostic info from the failing step:
- Failure analysis
- Screenshot
- Step trace, if the run was set to retain step traces
- DOM snapshot
- HAR file
Jira issue with mabl test diagnostics
How to link to existing issues
To link a mabl test or test run to an existing Jira issue, click on the + New issue or Create issue button and take the following steps:
- Issue Tracker: Select the issue tracker for this plugin
- Choose "Link existing"
- Project: Select the project containing the issue you want to link to
- Issue to Link: Search by the name of the issue or its Jira issue ID
- Append description (optional): To add additional information to the issue description, check the Append description box and add details.
Click on Submit to finalize the connection. A success message appears at the bottom of the screen in the mabl app. Click on the link to go directly to the Jira issue in a new tab.
Limitation
Linking to existing Jira issues is not supported for the Jira Server integration.
Jira shows the associated tests and test runs in the "mabl" section of the issue.
Associating mabl tests with test cases
If your team uses Xray for Jira or Zephyr, you can also link mabl tests and test results to a test case ID.
Note that linking mabl tests and test runs through the Jira integration does not establish an automatic sync between mabl tests and your test case IDs. To establish continuous reporting between mabl and your test case management tools, use one of the following options:
- Xray for Jira: Xray results reporting
- TestRail: TestRail integration
- Zephyr: Zephyr integration
How to manage Jira issues in mabl
You can review all Jira issues from the issues page - Tests > Issues - or from the Issues tab of a specific test.
- Click on the Jira link to review the related issue in Jira and request updates.
- Re-run the mabl test to reproduce the issue or validate a fix.
Note on Jira statuses
mabl only shows “Open” and “Closed” statuses for linked Jira issues. If a linked Jira issue has a status other than "Closed", such as "Pending", "Done" or "Shipped", it will appear as an "Open" issue in mabl.
Unlinking issues
When you no longer need to associate a Jira ticket with a mabl test, you can unlink it:
- Go to the test details page for the mabl test that is associated with the Jira ticket.
- Click the Issues tab.
- Select the issue(s) you want to unlink.
- Click on the Unlink button at the top of the page.
- Confirm the action in the modal.
How to build tests from Jira issues
If a Jira issue already describes the behavior you want to test, such as a user story, bug report, or requirement, you can hand it to the mabl agent when building a new test or editing an existing one. When your workspace has a Jira Cloud integration, the + menu below the prompt on the Build tests page includes a Jira issue option.
- Go to Build tests and, on the New test or Edit test tab, click + below the prompt and choose Jira issue.
- If the integration covers more than one Jira project, choose the project to search. Search covers one project at a time.
- Search by issue summary or issue key, such as
PROJ-123, then pick the issue. Each picked issue appears as a chip. You can add up to five. - Describe anything the issues don't cover, such as test data or the starting state, and send the prompt.
If you already have the issue key or URL, such as PROJ-123, paste it into the search box. mabl looks it up across every connected Jira site, so you don't need to choose a project first.
The agent reads each issue's summary and description. It never reads comments, attachments, or custom fields, and it can only read issues in the projects your integration is configured for. If your team keeps acceptance criteria in a custom field, include them in your prompt or attach a requirements file.
Limitation
Building tests from Jira issues is not supported for the Jira Server integration.