We’re upgrading the Testmo for Jira app from Atlassian’s Connect platform to their newer Forge platform. This is a required change – Atlassian is sunsetting Connect in Q4 2026, and we are aiming to ensure that all Connect-based Testmo apps are fully migrated ahead of that deadline.

The good news: the upgrade is straightforward, your data is fully preserved, and the core Testmo experience in Jira remains the same. As the Testmo admin responsible for your Jira integration, you’ll need to take a few steps to complete the upgrade. This article walks you through everything.

Why This Is Happening

Atlassian has announced that the Connect platform – the technology underlying the current Testmo for Jira app – will reach end-of-support in Q4 2026. After that date, Connect-based apps will no longer function.

Forge is Atlassian’s modern app platform, offering improved security, better performance, and a longer-term supported foundation. Migrating now means your team’s Jira-Testmo integration continues without interruption.

Timeline

Milestone	When
Available for new trials & customers	Now! ✅
Beta program (invite-only)	Soon – aiming for June
General availability (GA) – existing customers can upgrade	TBC – aiming for July
Reminder communications for unmigrated installations	Q3 2026
Migration deadline – Connect end-of-support	Q4 2026

You can upgrade your Jira app any time between GA launch and the Q4 2026 deadline. We recommend doing so promptly after GA to give yourself time to work through any questions before the deadline.

What Changes, What Doesn’t

What stays exactly the same

• All your existing test data, results, and configurations
• The same Testmo for Jira Marketplace listing — no charge for the app
• Core functionality: issue panels, test result display, Jira issue creation from Testmo, project-level configuration

What’s different after migration

For Jira admins:

• One-time setup step required. Immediately after upgrading the app, you’ll need to visit the Testmo admin configuration page and click “Complete Setup.” This finalizes your installation on the Forge platform. It takes under a minute.
• Project visibility configuration may look slightly different in the admin UI — same capabilities, different interface.

For your Testmo & Jira users:

• Account linking (one-time, per user). The first time each user opens a Testmo panel in Jira after migration, they’ll be prompted to link their Testmo account via OAuth. This takes under a minute and only happens once. 

If you’re a new customer, you won’t need to upgrade your Jira app. You can just install it and start using straight away!

If you’re an existing customer who’s been with Testmo for a while, you’ll probably need to upgrade your app using the migration steps below:

Migration Steps (Jira & Testmo Admin Privilleges Required)

The full migration takes 10–15 minutes. Here’s what you’ll do:

Step 1 — Upgrade the app (< 2 minutes)

• Go to Jira Settings → Apps → Manage Apps
• Find Testmo for Jira
• Click the Update button (this will appear once your account is enabled for the Forge version)
• Review and approve the app’s Forge permission scopes
• Wait ~30 seconds for the upgrade to complete

The “Update” button will appear for your account when we enable your installation for the Forge version. If you don’t see it yet, it means your account hasn’t been enabled yet — check back or contact us.

Step 2 — Complete admin setup (2–5 minutes)

• After upgrading, navigate to Manage Apps → Testmo App → Configure.
• Click the Complete Setup button needs to finalise the configuration.
• The system will finalize your tenant registration and capture your Jira site details
• Optionally: review and configure which Jira projects have Testmo enabled

Note: Step 2 is required as part of the new Forge security procedure. If you skip it, Testmo features won’t work correctly.

Step 3 — Re-authorize your Jira connection in Testmo

• Go to Testmo admin → Settings → Integrations → Jira
• Open your Jira Cloud connection
• Click “Authorize with Jira”. 

This reconnects Testmo’s own link to your Jira instance under the new Forge credentials. Without this step, creating or linking Jira issues from Testmo will fail. Use “Test connection” in the dialog to confirm it’s working before saving. If you have more than one Jira Cloud connection configured in Testmo, repeat this for each one.

Step 4 — Verify everything works (5–10 minutes)

After completing setup, run through these checks:

• Open a Jira issue that has Testmo data — confirm the panel loads and displays test results correctly
• Check that your project-level Testmo configuration looks right
• If you have GitHub, GitLab, or other integrations linked, spot-check that these continue to appear as expected

If anything looks wrong, see the troubleshooting section below, or contact support.

What Your Users Will Experience

You don’t need to do anything to prepare your users in advance — but it may be helpful to let them know that they’ll be asked to link their Testmo account the first time they use a Testmo panel after migration. This is a one-time OAuth step and takes under a minute.

Troubleshooting

• The “Update” button isn’t showing in Manage Apps. Your account may not yet be enabled for the Forge version. Contact Testmo support and we can check your migration status.
• After upgrading, the Testmo panel in Jira shows a login prompt, or user not linked error. Make sure you completed the admin setup step (Step 2 above). If you did and still see errors, check that your project-level configuration is set correctly in the Testmo admin screen.
• A user says they can’t see test results in their issue panel. Ask them to open the panel and follow the “Link your Testmo account” prompt. This is a one-time step required per user after migration.
• We need to roll back to the Connect version. Rolling back from Forge to Connect is not supported by Atlassian. If you encounter a critical issue after migrating, contact Testmo support.

Support & Resources

• Testmo for Jira App Migration guide
• Support