Atlassian Connect support ends 31 January 2027, but admin pages still show a December date

Atlassian will drop support for apps built on its Connect platform on 31 January 2027, and warning banners have started appearing in admin screens on Jira and Confluence sites. According to a dev.to article by Mihai of Lean Zero, the message is getting through unevenly: a single Atlassian page can show two different deadlines, older documentation still says December 2026, and the admin tooling offers no direct way to tell Connect apps apart from their Forge replacements.

A deadline that moved, while some messages did not

Atlassian pushed the cutoff back on 3 August 2026 in a post titled "Getting Ready for Connect End of Support", extending it from December 2026 to 31 January 2027; the developer changelog repeated the new date on 7 August. Pages revised afterwards carry the new date, including the admin-facing and migration documentation updated in August and September.

Older material was never revisited, though. The March 2025 timeline post still says "Q4 CY2026", an August 2025 post about custom apps says "the end of 2026", and some vendor support pages still quote December. The dev.to author found the same inconsistency inside the product: on a test site inspected on 16 October 2026, the Connected apps banner said apps would be unsupported after January 2027, while the tooltip on the same page's "Legacy" tag said the app may stop working after December 2026.

What the warnings actually mean

Atlassian's documented admin copy, on a page last updated 10 September 2026, reads "This app is running on a platform that will be unsupported after January 2027". Variants circulate: Exalate's support post and admins on Figma's and Lucid's forums quote "This app may stop working after January 2027". All three refer to the same Connect end of support. The phrase "This app might stop working soon" comes from a May 2026 developer-community thread about a banner shown inside apps; Atlassian staff said it was meant only for non-Marketplace apps, withdrew it the same day, and later said it had been limited to canary tenants.

One detail catches people out: an app can already be on Forge and still be flagged. Under the rule set out in Atlassian's March 2025 timeline post, an app with a Forge manifest plus a mix of Connect and Forge modules counts as a Connect app until every Connect module is removed. Exalate said in September that its package still ships a Connect component alongside its Forge implementation. A vendor saying it is already on Forge and the warning banner can both be true at once.

How to audit a site

The Connected apps screen, reached through Atlassian Administration by selecting Apps, then Sites, then the site, and requires organization or site admin rights. The old in-product Manage apps screen now redirects there. The list has no Connect or Forge column or filter; the only signal is a yellow "Legacy" tag, and the word Connect appears only inside a tagged app's details.

On the dev.to author's test site, 4 of 57 entries across three pages were tagged, all third-party Marketplace apps: ScriptRunner for Jira from Adaptavist, Navigation Menus for Confluence from Seibert, STAGIL Navigation Menus and Themes from STAGIL by catworkx, and User Management for Confluence from TechTime Initiative Group.

Opening a tagged app's details shows a panel whose colour, not its wording, carries the vendor's status: blue when the vendor has declared to Atlassian that it will migrate to Forge before end of support, yellow when it declared no, is undecided or said nothing. Atlassian staff have described the risk signal as complicated and conservative and told admins to expect false positives, so a tag means "look at this one", not that the app is doomed. Atlassian's own twelve Connect integrations on the test site, with versions ending in -AC, carried no tag and no statement on whether the deadline applies to them.

What remains is largely vendor outreach. When a Figma admin asked on Figma's forum on 9 October what the notification meant, Figma replied the next day that it plans to move Figma for Jira to Forge by the end of the year, the kind of answer, as the dev.to author notes, only the vendor can give.

Why it matters

Any Jira or Confluence app still carrying Connect code may stop working after the cutoff, and migration depends on individual vendors rather than Atlassian. The practical job for admins is a site-by-site sweep of Legacy tags, a read of each vendor's declared migration status, and follow-up with the ones showing yellow panels. Because tooltips, 2025-era posts and several vendor pages still say December 2026, treating the earlier date as the working deadline is the safer assumption. And since Atlassian's own integrations go untagged while mixed Forge-and-Connect apps get flagged, a clean-looking Connected apps page is not yet proof that a site is in the clear.