Forge Transition Roadmap

To give you better clarity about how and when we’re going to transition our apps to Forge, we’re sharing our intended dates when the transition will be completed. Please also read our Statement Regarding Forge Transition for further details.

Legend

  • Connect on Forge denotes Apps that already run on Forge while still partly using Connect modules

  • Forge denotes Apps that have fully migrated to Atlassian Forge

App

Current Status

Forge Transition Roadmap

Advanced Bulk Edit for Jira

Connect on Forge

Forge Q4 2026

Comment Custom Fields for Jira

Connect on Forge

Forge Q2 2026

Comment History Log for Jira

Connect on Forge

Forge Still undecided

Deep Clone for Jira

Forge

-

Dynamic Custom Fields for Jira

Connect on Forge

Forge Still undecided

External Data for Confluence

Connect on Forge

Forge Q4 2026

External Data for Jira Fields

Forge

-

Google Calendar for Confluence

Connect on Forge

Forge Q3 2026

Merge Agent for Jira

Connect on Forge

Forge Q2 2026

Quick Filters for Jira Dashboards

Forge

-

Slack for Confluence

Connect on Forge

Forge Q4 2026

Snipe-IT for Jira

Connect on Forge

Forge Q3 2026

Version Sync for Jira

Connect on Forge

Forge Q2 2026

Non-Forge Apps may still be available after 2026

Please note that while Connect has been announced to become “End of Support” by the end of 2026, Atlassian has not yet clarified when Connect will actually become unavailable. So while we don’t have any guarantees how much longer Connect apps will keep working, chances are that they will keep working after the end of support date. We will proactively notify customers of any apps that have not been transitioned to Forge by the end of 2026 once Atlassian announces any Connect end of life dates.

This should only affect customers of our Comment History Log for Jira and Dynamic Custom Fields for Jira apps, where we have not yet decided if and when they will be fully transitioned to Forge.