Kayabyte

Atlassian Connect end of support: what Jira and Confluence admins should check before 31 January 2027

By Kayabyte · Updated 3 November 2026

Short answer: Atlassian Connect, the older way of building Cloud apps, reaches end of support on 31 January 2027. Atlassian doesn’t say every Connect app stops working that day, but it will only address critical security patches from then on, and it warns that breakages will become more frequent and some platform changes will stop apps without advance notice. Admins should list their apps, check the warning on the Connected Apps page, ask each vendor for a migration plan, and test any replacement before the date, starting with the apps that billing, payroll or support depend on.

This page is for site admins, not developers. Facts about Connect come from Atlassian’s own posts, linked below; things change, so check them before you rely on a date.

What changes on 31 January 2027

Atlassian’s post says that from this date:

Atlassian has said it will share more on what happens after end of support, and hasn’t yet given those details.

The checklist

  1. List your apps. Copy the list from your site’s Connected Apps page in administration. Note who uses each app and who owns it.
  2. Read the warning. That page shows a Connect end of support warning for apps it applies to. A vendor can replace the generic text with its own message and a link to its migration plan.
  3. Don’t panic at a flag. Atlassian’s developer advocate has called the “at risk” flag “a blurry signal” that can produce false positives. It’s a reason to check, not a verdict.
  4. Ask the vendor three things. Is the app fully on Forge today? If not, by what date? Does anything stop working or change after the move?
  5. Check independently if you want. forge-apps.com shows the Forge status of released Marketplace versions. It isn’t run by Atlassian and doesn’t show a vendor’s intentions.
  6. Check what the move removes. Vendors’ own notes show that some features don’t survive a migration, so read the change notes for what your team uses.
  7. Rank by damage. Rank apps by what breaks if they stop without warning. Reports used for invoices, payroll, audits and SLAs come first.
  8. Test before you need it. If you may have to change app, compare old and new on one closed period and one real project. Leave time for this: a month-end report needs at least one month-end to compare.

Questions for reporting and cost apps

Reports fail quietly, so these need a closer look:

Which of our apps this affects

None of the Kayabyte apps. Burnrate, Group Participants, Group Watchers and Personal WIP Limits were all built on Forge from the start, so there’s no migration to wait for. Burnrate is the one that matters for this topic: it prices native Jira worklogs with dated rates and shows budgets. It’s new, with no reviews, so test it against a closed month as above. It’s on the Atlassian Marketplace.

FAQ

When does Atlassian Connect end? End of support begins on 31 January 2027. The date was moved from December 2026.

Will my Connect apps stop working on 31 January 2027? Atlassian doesn’t say that all of them stop on that date. It does say breakages will become more frequent and that some platform changes will stop apps without advance notice.

How do I know if a Marketplace app is on Connect or Forge? Look for the warning on the Connected Apps page in site administration and ask the vendor. forge-apps.com, which isn’t run by Atlassian, also shows the status of released versions.

What does the “at risk” banner mean? It’s based on an app’s migration status and the intent its vendor has declared. Atlassian describes it as a blurry signal that can produce false positives, so ask the vendor before you replace an app.

What should I do first? List your apps, rank them by what would break if they stopped without warning, and ask the vendors of the top ones for a migration date.

Jira, Confluence and Atlassian are trademarks of Atlassian. Kayabyte is an independent developer and is not affiliated with or endorsed by Atlassian.