Guides for Jira teams

Guide · Connect end of support

Magic Estimations and the end of Connect: keep estimating in Jira

If your team sizes the backlog with Magic Estimations on Jira Cloud, here is what Atlassian's move away from Connect means for it, why your estimates are already safe, and how to switch between two refinements.

What is changing

  • Connect end of support is 31 January 2027. After that date Atlassian no longer supports Connect apps, and they may stop working as the platform changes.
  • Connect apps can no longer ship updates through the Marketplace since spring 2026.
  • Jira has started telling admins, and then users, when an installed app "might stop working soon".

Apps built on Forge, Atlassian's current platform, are not affected.

Is your Magic Estimations affected?

On the Atlassian Marketplace, both Magic Estimations – Async and Planning Poker sizing for Jira and Magic Estimations Lite by Magic Apps are listed as Connect apps: their latest cloud versions are 1.4.13-AC and 1.0.10-AC (the -AC ending marks Connect), both released on 23 March 2025, as of November 2026. Two ways to check your own site:

  • In Jira, open Apps → Manage your apps and look for the "might stop working soon" notice next to Magic Estimations.
  • Ask Magic Apps, the vendor, whether a Forge version is planned and when. If one is coming, the simplest path may be to wait for it.

Your estimates live in Jira

The result of an estimation is the number written to Story points (or the field you chose) on each issue. That stays in Jira whatever happens to the app. What you lose with the app is the way of running a session: the scale, the silent sorting, the reveal.

A calm way to switch

  1. Note how you estimate today

    The scale (Fibonacci, T-shirt sizes), the field the result goes to, and whether you sort silently or vote card by card.

  2. Install the replacement next to the old app

    Both can run side by side.

  3. Run your next refinement in it

    Same scale, same field, the same backlog query.

  4. Compare the outcome

    If the numbers land in the same field and the team is happy, the switch is done.

  5. Uninstall Magic Estimations

    Past estimates stay on the issues.

Choosing a replacement

  • Built on Forge (look for "Runs on Atlassian" or ask the vendor), so you don't face the same move again.
  • Silent, relative sorting if that is how your team works, not only planning poker one card at a time.
  • Writes to your field, with the facilitator's Jira permissions.
  • Works remotely and asynchronously, if your team doesn't meet at the same time.

Planning poker apps on Forge are plentiful. For silent sorting, YTI Magic Estimation (made by us, YTI Digital) is one option: everyone places every issue on the scale without seeing the others, outliers come first after the reveal, each issue starts at the median, and one click writes the results to Story points or any number field. It runs on Forge, and nothing leaves Atlassian. Its switching page maps the terms, and Magic estimation in Jira Cloud, step by step explains the method.