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, now that we have declared our plans, an informational notice that the app is being migrated, linking to this page.

This page explains what that message means, why it appears for our app, and what we are doing about it.

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 is one of those apps. Today it is built on Connect: both project tabs — Replay and Statistics — are delivered through Connect modules. That classification is accurate — we have not migrated the app yet.

What has changed is that we have now declared our intent to Atlassian. That is why the generic "may stop working" warning is replaced by a notice pointing here.

Will the app stop working?

No. We are migrating Retrospective Tools to Forge before the deadline, and we have recorded that commitment with Atlassian in a form they publish to you.

There is no plan to sunset Retrospective Tools. It remains supported, and it will continue to be available on the Atlassian Marketplace (opens in a new tab) throughout the migration.

Will I need to do anything?

Almost certainly not.

• You should not need to uninstall and reinstall the app. Atlassian's migration path upgrades a Connect app to its Forge successor in place, on the same Marketplace listing and the same licence.
• Your existing views and configuration will continue to work.
• The app's behaviour will not change. Retrospective Tools does exactly the same thing before and after the move — this is a change of platform, not of product.

The one thing that may need your attention is permissions. If the Forge version of the app requests a scope that the Connect version did not, Atlassian will ask an administrator to approve it in the usual way. We will say so in advance if that happens.

What the migration involves

Retrospective Tools is unusually well suited to Forge, because of how it already works: all computation happens in your browser, and no Jira data is ever sent to our server (see our Data Security and Privacy Statement). Our backend only serves the app's front end and handles the Connect install handshake.

That means the migration does not involve moving a data pipeline or re-architecting a backend. The work is to rebuild the app's modules as native Forge equivalents:

Our timeline

We will keep this page updated as each phase completes.

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)