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 |
|---|---|---|
|
Connect on Forge |
Forge Q4 2026 |
|
|
Forge |
|
|
|
Connect on Forge |
* See below |
|
|
Forge |
|
|
|
Connect on Forge |
* See below |
|
|
Connect on Forge |
Forge Q4 2026 |
|
|
Forge |
|
|
|
Forge |
|
|
|
Forge |
|
|
|
Forge |
|
|
|
Connect on Forge |
Forge Q4 2026 |
|
|
Connect on Forge |
Forge Q4 2026 |
|
|
Forge |
|
* Forge Transition for Comment History Log for Jira and Dynamic Custom Fields for Jira
Together with another established Atlassian Marketplace partner, we’re actively working towards securing long-term Forge support for these apps. More details will be shared by the end of October 2026. In the meantime, Connect support is guaranteed by Atlassian until January 31, 2027.