Atlassian is moving Cloud apps from Connect to Forge, its current platform for building apps for Jira and other Atlassian Cloud products. As part of this transition, Atlassian will end support for Connect on January 31, 2027.
You can read more in Atlassian’s official announcement: Getting Ready for Connect End of Support.
ActivityTimeline is already in the process of migrating to Forge and is on track to complete the transition ahead of this deadline.
This page provides information about our migration progress, what is changing, and what ActivityTimeline customers need to know.
Current status
The first migration step has been completed, and ActivityTimeline Cloud app is currently running in Connect-on-Forge mode where some modules are already migrated to Forge and some are still on Connect.
We are now working on the final stage of the migration. By October 30, 2026, we plan to complete the transition to pure Atlassian Forge without any legacy Connect modules.
Do customers need to take any action?
No action is required as of now.
The migration is being handled by the ActivityTimeline team, and customers do not need to manually migrate their data or configuration.
You may currently see a Legacy or Connect end-of-support notice for ActivityTimeline in Atlassian Administration or Jira. This notice relates to the underlying Atlassian Connect technology that ActivityTimeline is transitioning away from.
It does not mean that ActivityTimeline is being discontinued.
Once our Forge migration is completed and the corresponding Atlassian requirements are met, ActivityTimeline will no longer rely on the legacy Connect framework.
You may see an “Update” button on the Jira’s Configuration → Marketplace Apps page to manually update the app to the latest version if it was not automatically updated.
Will anything change?
Our goal is to keep the transition as seamless as possible and preserve the existing ActivityTimeline experience.
However, because Forge and Connect have significant technical differences, a small number of existing integration points may work slightly differently after the migration.
Due to the current limitation of Forge support on Jira mobile app, ActivityTimeline Log Work action will no longer be available in the Jira mobile app after the Forge migration, as the required functionality is not currently supported by Atlassian for Forge apps on mobile.
Logging work through ActivityTimeline in Jira on the web will remain available as usual. We will continue to monitor Atlassian’s Forge mobile capabilities and intend to restore this functionality once the necessary support becomes available.
Stay updated
We will keep this page updated with the latest migration status and any customer-facing changes.
Our current target is to complete ActivityTimeline’s Forge migration by October 30, 2026 (or sooner), ahead of Atlassian’s Connect End of Support.
If you have questions about the migration or how it may affect your ActivityTimeline environment, please contact our Support team.