Skip to main content

2026/11/05 - Upgrade the mabl Jira Cloud app to version 4

Docs integration
  • Updated

Jira admins: the mabl Jira Cloud app now runs on Atlassian Forge as version 4.x. Atlassian is retiring Connect, the platform that version 2.x and earlier of the app were built on. If your Jira Cloud site still runs one of those versions, an organization admin or site admin needs to approve the upgrade to 4.x by January 31, 2027. After that date, the older version stops working, and you can't create or link Jira issues from mabl until you upgrade.

Who is affected

  • Affected: Jira Cloud sites running version 2.x or earlier of the mabl app.
  • Not affected: Jira Cloud sites already on version 4.x.

To check which version your site runs, open Connected apps in Atlassian Administration and find mabl: Automated Testing with Jira & Rovo. If it shows an Update label, your site is on an earlier version and needs the upgrade.

The mabl app in Connected apps with the Update label

When you upgrade, your integration settings, connected workspaces, and linked issues carry over.

Upgrade the app

An organization admin or site admin approves the upgrade in Atlassian Administration and reviews the app's new Jira permissions along the way. For the steps and the permission changes, see Upgrade from an earlier version of the app.

Atlassian sets the version numbers for Forge apps, which is why the app goes from 2.8.0 to 4.4.0.

What you get in 4.x

  • Status sync in both directions: Closing a linked Jira issue closes its mabl issue for any status in Jira's Done category, such as "Resolved", in every Jira language. Reopening the Jira issue reopens the mabl issue. Previously, only statuses named "Done" or "Closed" closed the mabl issue, and reopening had no effect.
  • Project search on large sites: Type a project's name in the Project dropdown in mabl to find any project on your site.
  • Names in English: Issue types and statuses always show in English in mabl.
  • Formatted descriptions: Headings, code blocks, and line breaks in mabl issue descriptions display correctly in Jira.
  • Append description: When you link an existing issue, Append description adds your text to the current Jira description.
  • No duplicate attachments: Relinking an issue attaches files only from new test runs.

Version 4.x also tightens how the app authenticates calls from mabl.

Learn more

For questions about the upgrade, reach out to your customer success manager at mabl.

Related articles