How to check which Jira apps are affected by Connect end of support
Updated by Pledona
Atlassian ends support for Connect, its older framework for cloud apps, on January 31, 2027. Since the summer of 2026, Jira admins have been seeing yellow and blue banners and a LEGACY tag on some apps. Here is how to find every affected app on your site, what each message means and what to do before the deadline.
What changes on January 31, 2027
- Only critical security fixes. After that date Atlassian will only address critical security vulnerabilities in Connect, and Connect features can be deprecated with little notice.
- No hard switch off date for your app. Atlassian's 2025 timeline says customers with Connect apps installed won't lose access to them, but Connect will stop evolving with Jira, and as the platform changes some apps may stop working properly.
- Pure Connect apps are already frozen. New Connect apps stopped being listed on the Marketplace in September 2025, and since March 2026 apps with only a Connect descriptor can no longer receive updates. A Connect app that still gets new versions has adopted a Forge manifest.
- Mixed apps count as Connect. Atlassian treats an app with a Forge manifest and a mix of Connect and Forge modules as a Connect app until every Connect module is removed.
Step 1: open Connected apps
You need to be a site admin or organization admin. There are two ways in:
- In Jira, select Apps, then Manage your apps. This opens the Connected apps page.
- In Atlassian Administration, open Apps, choose your site, then Connected apps.
The list has no column or filter that says Connect or Forge. The signal is the status tag on each app and the message under the app's name. Atlassian's list of tags includes LEGACY, which it describes as a legacy app approaching end of support, and UPDATE, which means a newer version is waiting for you.
Step 2: read the message under each app
Atlassian publishes the exact wording admins see. The colour and text tell you where the vendor stands:
| What you see | What it means | What to do |
|---|---|---|
| No message | A Forge app with no Connect features | Nothing for this deadline |
| Yellow: "This app version is running on a platform that will be unsupported soon. Update your app now..." | Your installed version runs on Connect, but the vendor has published a newer version with a Forge manifest | Update the app, then check the message again |
| Blue: "This app is running on a platform that will be unsupported after January 2027. Learn more about the vendor's plans..." | The vendor has told Atlassian it will move to Forge before end of support | Read the vendor's plan and note its dates |
| Yellow, with the same text and a link to the vendor's plan | The vendor has declared it is undecided, or that it will not migrate before the deadline | Read the plan and ask the vendor directly |
| Yellow: "This app is running on a platform that will be unsupported after January 2027. For migration plans or other available options, contact the vendor..." | A Marketplace app on Connect whose vendor has declared nothing | Contact the vendor through the app's Marketplace listing |
| Yellow message plus a LEGACY tag on an app you built or commissioned | A private (custom) app still on Connect | Audit it and plan a rebuild or removal (Step 5) |
One caution: Atlassian keeps a small group of apps out of this messaging while it fixes a platform gap they depend on. So no message almost always means Forge, but not always. If an app matters, confirm it with Step 3.
Step 3: double check on the Marketplace
- Descriptor link. Atlassian's knowledge base suggests opening the app's Marketplace listing and scrolling to Resources. A Descriptor link there means a Connect descriptor; no Descriptor link points to Forge.
- Runs on Atlassian badge. Only Forge apps can carry it, because it requires Atlassian hosted compute and storage with no outside data egress. Many good Forge apps do not qualify, so a missing badge proves nothing.
- Ask the vendor. For anything business critical, a written answer with a date beats any screen.
Step 4: write an inventory
For every app with a yellow or blue message, record the app name, the message colour, whether it is a Marketplace or private app, who on your team owns it, what workflow depends on it, how much data lives in it (fields, macros, settings, history) and a decision date. Work backwards from January 31, 2027 through your own change windows, and give your service desk a short answer for users who ask whether an app is about to break: the message is a deadline notice, not an outage.
Step 5: decide per app
- Marketplace app, blue message: usually nothing to do except keep the app updated. Atlassian says admins with Marketplace Connect apps need no action at this stage, because migration is the vendor's job.
- Marketplace app, yellow message: ask the vendor for a migration date through the listing. If the answer is no or nothing comes back, shortlist a Forge replacement now and export what you need from the old app first, while its screens still work.
- Private app with a LEGACY tag: Atlassian recommends checking what it does, who uses it and whether a native Jira feature can replace it. If you still need it, contact the developer (shown in View app details) or an Atlassian Solution Partner to rebuild it on Forge. If not, tell users and uninstall it before January 31, 2027.
A common case: Jira notifications in Google Chat
Google's Chat app for Jira Cloud is the most installed way to get Jira updates into Google Chat. Its Marketplace listing shows a Connect app whose latest Cloud version, 1.1.0-AC, was released on November 11, 2021 (Atlassian Marketplace data, checked October 20, 2026). Google has not published a Forge plan that we could find, so check the message on your own Connected apps page and ask Google if you depend on it. Two options that do not use Connect: a Jira Automation rule that posts to a Google Chat incoming webhook (see Jira Automation webhook examples), or a Forge app. Threadline for Jira is built on Forge with no Connect modules, adds filters, threads, digests and quiet hours and is pending Atlassian Marketplace review.
Pledona apps and Connect
All three Pledona apps were built on Forge from the start and contain no Connect modules, so they should show no end of support message. Pledona Export exports Jira issues to Excel, CSV and PDF entirely inside Atlassian and is pending Atlassian Marketplace review. Proofline adds test cases, cycles and CI result import inside Jira and is pending Atlassian Marketplace review.
Sources: Atlassian developer docs, What admins see on the Connected Apps page (updated September 10, 2026) and Connect End of Support: What it means for private/custom apps. Atlassian blog, Getting Ready for Connect End of Support and Announcing Connect End of Support: Timeline and Next Steps. Atlassian Support, View and filter installed apps and How to identify if an app is Forge or Connect. Atlassian Community, Connect warnings are about to reach your admin console. Google app data from the Google Chat for Jira Cloud listing.
Frequently asked questions
When does Atlassian Connect end of support start?
January 31, 2027. Atlassian extended it from December 2026. After that date it will only address critical security vulnerabilities in Connect, and Connect features can be removed with little notice.
What does the LEGACY tag mean in Connected apps?
Atlassian describes LEGACY as a legacy app approaching end of support. It marks apps that still run on Connect, and Atlassian uses it especially for private or custom apps.
Will my Connect apps stop working on January 31, 2027?
Atlassian has not announced a switch off for that day. It says customers won't lose access, but Connect stops evolving with Jira, so features can break or be removed with little notice. Treat the date as a deadline to plan around.
How can I tell if a Jira app is Forge or Connect?
Check the message under the app on the Connected apps page: a pure Forge app shows none. You can also open its Marketplace listing and look for a Descriptor link under Resources, which means Connect, or ask the vendor.
Do I need to do anything about Marketplace apps with a warning?
Atlassian says no action is required from admins at this stage, because vendors handle the migration. Still update the app if a newer version exists, and ask the vendor for a date if the message is yellow.