As Connect End of Support (EOS) approaches, Atlassian is adding in-product messages to the Connect modules your customers use every day. These messages appear inside your app's UI in Jira and Confluence, and are shown to both end users and admins. This page explains which apps show in-product messages, where they appear, and which message each audience sees for each migration intent.
In-product messages are separate from the messaging on the Connected Apps admin page. For the admin page experience, see What admins see on the Connected Apps page.
Connect will no longer be a supported platform from 31 January 2027 and onwards. This date was extended from December 2026 to give partners and developers additional time to prepare over the holiday period.
After this date, Atlassian will only address critical security vulnerabilities in Connect, and Connect feature deprecations will happen with little notice. Connect will not remain in a steady state after end of support.
For the full timeline, read Getting Ready for Connect End of Support.
In-product messages roll out in two stages:
Atlassian announces each stage in the changelog.
In-product messages appear in Connect apps and Forge apps with Connect modules that:
NO in the connectToForgeMigration module.UNDECIDED in the module.connectToForgeMigration module.
This includes apps with only a Connect descriptor.In-product messages do not appear for:
YES.
These apps still show messaging on the Connected Apps page.To share your plans with customers, set willMigrateToForgeBeforeEOS (your migration intent) and migrationGuideUrl (a link to your migration plan) in the connectToForgeMigration module.
If your app is still a Connect app, adopt Forge first, because the module is only available in a Forge manifest.
Until you declare an intent, the in-product message sends users to your Marketplace listing's support tab, so keep your support details current.
In-product messages appear in Connect modules only. Atlassian uses two presentation styles, depending on how much space the module has.
| Style | How it looks | Used in |
|---|---|---|
| Section message | A warning panel at the top of the module, with the message and its actions. | Modules with room for a panel, such as full pages and macros. |
| Inline message | A warning icon next to the module. Hovering shows a short summary, and selecting the icon opens the full message and its actions in a dialog. | Compact modules, such as the Confluence content byline and the Jira issue context panel. |
The message a user sees depends on:
Each combination has its own message.
In the messages below, App name is replaced with the name of your app.
What end users see:
App name will no longer be supported or updated after January 2027. If you rely on this app, let your site admin know so they can plan an alternative.
What admins see:
App name will no longer be supported or updated after January 2027. Review the app developer's plans for more information. Check Connected apps to see more details.
What to do: keep your migrationGuideUrl up to date so customers can find out what to use instead.
What end users see:
App name might stop working because it is running on a platform we'll no longer support after January 2027. Review the app developer's plans for more information. If you rely on this app for your work, contact your site admin.
What admins see:
App name might stop working because it is running on a platform we'll no longer support after January 2027. Review the app developer's plans for more information. Check Connected apps to see more details.
What to do: update your migration intent to YES or NO as soon as your plans are confirmed, and keep your migrationGuideUrl up to date.
What end users see:
App name might change or stop working because it is running on a platform we'll no longer support after January 2027. The developer has not provided a migration plan. If you rely on this app, contact the developer to ask about their plans or contact your site admin.
What admins see:
App name might change or stop working because it is running on a platform we'll no longer support after January 2027. The developer has not provided a migration plan. If you rely on this app, contact the developer to ask about their plans or review your options in Connected apps.
Contact the app developer sends the user to the support tab of your app's Marketplace listing. If the app has no Marketplace listing, for example a private app, the message shows a note instead:
What to do: declare your migration intent so customers see your plans instead of this message, and keep your Marketplace support details current. For private apps, read Connect End of Support: What it means for private/custom apps.
Rate this page: