Migrating Testmo for Jira to Forge

Why this guide exists

Atlassian is retiring the Connect platform — the technology the current Testmo for Jira app runs on — in Q4 2026. After that date, Connect-based apps will stop working in Jira.

We've built the Forge version of Testmo for Jira and are rolling it out ahead of the deadline. This migration is required for all customers before Q4 2026. This guide explains what you need to do, what will change, and what won't.

What stays exactly the same

• All your test data — nothing to export, migrate, or re-import
• The same Testmo for Jira app on the Atlassian Marketplace (same listing, reviews, and ratings)
• Core functionality: issue panels, test results in Jira, Jira issue creation from Testmo, project configuration
• Pricing and licensing

What changes

For Jira admins — three quick steps at migration time:

1. Click "Update" in Manage Apps — upgrades the app from Connect to Forge. Takes under two minutes.
2. Click "Complete Setup" on the Testmo configuration page — a new required step that finalises your installation. Don't skip this: if you do, Testmo features won't work correctly.

For your Testmo users & admins — they need to link their accounts:

• Re-authorize the Jira connection — Testmo admins should go to Admin → Settings → Integrations → Jira & click the "Authorize with Jira", to approve the new Atlassian Forge based app authorization.
• One-time account linking — the first time each user opens a Testmo panel in Jira after migration, they'll be prompted to link their Testmo account via OAuth. It takes under a minute and should only need to be carried out once under normal conditions (the OAuth token should auto-refresh unless it's not used for a long period of time — in which case the user may need to re-authenticate).

How to migrate (step by step)

Time required: 10–15 minutes for an admin with access to both Jira & Testmo admin consoles.

Step 1 — Upgrade to Forge

Go to Jira Settings → Apps → Manage Apps, find Testmo for Jira, and click Update.

Note: the Update button only appears once your account has been enabled in our staged rollout. If you don't see it yet, your account is in the queue — it will appear when your account is enabled.

Step 2 — Complete the admin setup

After upgrading, you'll be redirected to the Testmo admin configuration page in Jira. Click Complete Setup. This step finalises your installation — don't skip it.

Step 3 — Re-authorize Jira Connection in Testmo

Navigate to **Testmo admin → Settings → Integrations → Jira

• Open the existing Jira Cloud connection
• Click "Authorize with Jira"
• Approve the OAuth permissions in the Atlassian popup (requests `jira-user` and `jira-work` access)
• Click "Test connection" to confirm the connection is working
• Save the connection
• If multiple Jira connections are configured, repeat for each one

Step 4 — Verify

Do a quick spot-check: open a Jira issue with Testmo data, check your project configuration, and confirm any GitHub or GitLab integrations are working as expected.

Step 5 — Let your users know (optional but recommended)

Before migrating, you may want to give your team a quick heads-up:

"We're upgrading the Testmo Jira integration. The first time you open a Testmo panel after the upgrade, you'll be asked to link your Testmo account — it takes under a minute. You may also see a brief security confirmation when clicking external links from Testmo. Both are expected."

Timeline

You don't need to migrate on day one of GA. We recommend doing it soon after GA opens so you have time to get familiar with any changes well before the Q4 deadline.

Join the beta

Want early access before general availability? We're looking for customers to join the beta programme — you'll get priority support during migration and the chance to share feedback that shapes the final release.

Sign up for the beta →

Spots are limited. Beta participants will be contacted with instructions once their account is enabled.