Migration to Atlassian Forge
Last updated
Summary
Magic Estimations currently runs on Atlassian Connect. Atlassian is ending support for the Connect platform on 31 January 2027, which is why Jira administrators see a notice on the Connected apps page.
We are moving Magic Estimations to Atlassian Forge, Atlassian's supported cloud app platform. The new version has been in development since 2025 as a complete rebuild of the app, designed to run entirely on Forge and carry the Runs on Atlassian designation — meaning app data stays inside Atlassian's infrastructure. It also builds on newer Forge platform capabilities such as Forge Realtime (generally available since June 2026) for live collaboration during estimation sessions.
The migration is fully automatic: you do not need to reinstall, reconfigure or re-purchase anything, and all your estimation data is carried over.
What this means for you
| Question | Answer |
|---|---|
| Will the app stop working? | No. The app keeps working throughout the migration and after 31 January 2027. |
| Do I need to do anything? | No. Updates arrive through the Atlassian Marketplace automatically. |
| Will my data be kept? | Yes. All sessions, boards, estimates, history and settings are migrated automatically. |
| Will the price or licence change? | No. Your existing subscription continues unchanged. |
| Will the interface change? | The first update keeps the current interface. The second update brings the new version of Magic Estimations (see below). |
| Where will my data be stored? | After the migration, app data is stored in Atlassian-hosted Forge storage instead of our own infrastructure. |
| I use Magic Estimations Lite — does this apply to me? | Not yet. The free Lite app stays on Connect for now and keeps working; its future is decided and announced separately — see below. |
Timeline
| Phase | When | What happens |
|---|---|---|
| 1. Transition release (v1.XX) | Q4 2026 | Same app, same interface, now delivered on the Forge platform. Runs on Atlassian's rollout schedule; no action required. In the background, your data is copied to Atlassian-hosted storage and kept in sync. |
| 2. New version (v2.0) | Q1 2027 | The new Magic Estimations, built natively on Forge and carrying the Runs on Atlassian designation. Your data is already in place when it arrives. |
| 3. Legacy infrastructure retired | Q2 2027 | Our previous hosting is switched off. We deliberately keep it running for a while after v2.0: it still serves Magic Estimations Lite until a decision on that app is made, and it lets us handle special cases — sites that could not be updated automatically or where data migration needs a manual check — without time pressure. Administrators of such sites are contacted directly. |
The currently planned dates of these releases are kept up to date on the Changelog page.
Features to be deprecated
The new version (v2.0) is a complete rebuild, and a few features of the current app will not be carried over:
| Feature | What changes | What to do |
|---|---|---|
| Chat panel | Discontinued in v2.0. Chat history is not migrated. | Copy anything you need from session chats before the v2.0 update. Use the issue comments or your team messenger for discussion. |
| App usage chart | Discontinued in v2.0. The daily-connections chart on Global configurations was fed by our own infrastructure, which is being retired. | Atlassian does not yet provide per-app active-user metrics for Cloud apps. Organizations with Atlassian Guard (Standard or Premium) or an Enterprise plan can see app activity in Atlassian Administration → Insights → Audit log — filter by the App actions category, activity Third-party app Jira API request. This is an activity signal, not a count of active users. |
| Send feedback popup | Discontinued in v2.0. The in-app feedback form created tickets in our service desk directly from the app; an app with the Runs on Atlassian designation does not send data outside Atlassian, so the popup is replaced by a link to our support portal. The Enable feedback notifications setting in Global configurations goes away with it. | Use the Magic Apps contact form for feedback and feature requests. |
| Anonymous usage data setting | Discontinued in v2.0. The app no longer runs its own analytics. The only external service it uses is error monitoring (Sentry), declared as an egress permission of the app and visible to admins on the app’s permissions page. | Whether installed apps may share such data is controlled in Atlassian Administration → Connected apps (analytics access, per app or for all apps) instead of inside Magic Estimations. |
| Short invitation links (mgst.me) | Discontinued in v2.0. Short mgst.me session links worked because our own infrastructure kept a registry of sessions resolvable by a short id. In the new version, sessions live entirely inside your Jira site, so there is no external service to resolve them; existing mgst.me links stop working with the v2.0 update. | The Invite participants copy button stays and copies the session's full Jira URL (as in the browser address bar). Re-share any short links you have saved in wikis or chats. |
| Fallback connection setting | Not needed on Forge: the app no longer uses our own real-time infrastructure, so the setting disappears from Global configurations. | No action required. Corporate proxies and firewalls only need to allow Atlassian domains. |
This table is updated together with the timeline as details of v2.0 are finalized.
Magic Estimations Lite
Magic Estimations Lite, the free edition for individual teams, is a separate Marketplace app. It stays on Atlassian Connect for now and keeps working as usual on our infrastructure; the notice on the Connected apps page applies to it as well, but no action is required from administrators.
This page covers the main Magic Estimations app only. The decision on the Lite app — whether and how it moves to Forge — is made separately and depends on how Atlassian implements its planned per-user seat licensing for Marketplace apps. Any announcement will be published on this page and on the Lite listing.
Recommendations for administrators
- Keep automatic app updates enabled for Magic Estimations (this is the Marketplace default).
- Around the date of the v2.0 update, ask teams to finish estimation sessions that are in progress. Sessions are paused briefly during the switch and resume afterwards; changes made in the last hour before the switch may take up to an hour to appear in the new version.
- If your site uses a Marketplace-issued licence token or a suspended subscription, the update cannot be applied automatically. We will contact you with a short manual procedure.
Questions
- Support: Magic Apps contact form
- Release notes: Changelog
- Atlassian's announcement: Connect End of Support: timeline and next steps