What is this warning?
If you are using Exalate on Jira Cloud, you may have recently noticed a banner in your Jira instance stating:
“This app may stop working after January 2027, as it’s running on a platform that will be unsupported from that date.”
Depending on your Jira instance, the date shown in the banner may vary — some customers are seeing December 2026, others January 2027. Either way, this refers to the same underlying issue.
This message is generated automatically by Atlassian and is related to their deprecation of the Connect platform — the underlying framework some Marketplace apps are built on.
Does this mean Exalate will stop working?
No. Exalate will not stop working in December 2026 or January 2027.
The warning appears because Exalate’s current app package still includes a Connect component alongside its Forge implementation. Atlassian displays this banner for any app that ships with a Connect component, even if — like Exalate — the app already runs on Forge.
What is Exalate doing about it?
We are actively working on a Forge-only version of Exalate for Jira Cloud that will fully remove the Connect component. Once released, this warning will no longer appear.
What do you need to do?
Nothing. Your sync will continue to work normally in the meantime. No configuration changes or migrations are required on your side.
We will notify customers when the Forge-only version is available.
More information
For background on Atlassian’s Connect deprecation, see Atlassian’s official announcement: Connect End of Support: What it means for Marketplace apps.
If you have questions or concerns, you can submit a support request to our Service Desk directly. Alternatively, you can send an email to support@exalate.com. This will create an issue on our JIRA Service Desk, allowing for further tracking.