Forge migration plan

If you administer Jira, you may have seen a message about Retrospective Tools on the Connected apps page in Atlassian Administration — either a warning that

This app may stop working after January 2027, as it's running on a platform that will be unsupported from that date.

or an informational notice that the app is being migrated, linking to this page.

This page explains what that message means, what has changed, and what — if anything — you need to do.

Why you are seeing this message

Atlassian is retiring Atlassian Connect, its older app platform, on 31 January 2027. It is replaced by Forge, the modern platform. To help administrators plan, Atlassian shows a notice on every app that still uses Connect.

Retrospective Tools has now moved to Forge. Both project tabs (Replay and Statistics) run as native Forge modules, and nothing is served through Connect any more. If you still see the notice, your site has not yet approved the latest update — approving it removes the notice.

The update that asks for your approval

Forge grants access through explicit, itemised permissions, so the Forge version of the app declares its access differently from the Connect one, and Atlassian asks an administrator to approve the update in the usual way on the Connected apps page.

It is read-only. The app cannot create, edit or delete anything in Jira. This is the Forge equivalent of the read access the Connect version already had.

If you do not approve, nothing breaks: your site stays on the version it has now. The Atlassian notice will remain, though, and the update needs to be approved before 31 January 2027.

What changes after the update

• You do not need to reinstall. The Forge version upgrades the Connect app in place, on the same Marketplace listing and the same licence.
• Your saved configurations come with you. They are copied into the Forge app's storage automatically when the update is applied, with a daily retry until the copy succeeds. They remain shared across all projects, exactly as before.
• Jira data is read as the signed-in user. Each person sees replays and statistics built only from issues they are permitted to see in Jira.
• Your data still never leaves Atlassian. All computation continues to happen in your browser (see our Data Security and Privacy Statement); the Forge version has no external backend at all.

If your saved configurations are missing

The copy runs by itself, but a Jira administrator can check on it or start it by hand: go to Jira settings → Apps → Retrospective Tools and open Saved configuration migration. The page shows whether the copy has completed and lets you run it again. If it reports a problem, please contact our support team.

Will the app stop working?

No. The migration was completed in September 2026, well before the January 2027 deadline. There is no plan to sunset Retrospective Tools. It remains supported, and it continues to be available on the Atlassian Marketplace (opens in a new tab).

Our timeline

The one remaining step is yours: approving the update on your site, at any point before 31 January 2027.

Questions

If you have questions about this migration, or you need something in writing for an internal review, please contact our support team. We are happy to help.

Further reading

• Atlassian: Connect end of support timeline (opens in a new tab)
• Atlassian: what the Connected apps messages mean (opens in a new tab)