The Atlassian Marketplace and Developer ecosystem is evolving from Connect Apps to Forge Apps. Atlassian has announced that Connect apps will enter End of Support at the end of 2026. To ensure continued support, the eSign apps by Digital Rose will transition to this new platform.
The Atlassian Forge platform introduces some exciting new capabilities to integrate within Jira and Confluence. But the new platform does not support everything that the legacy Connect platform did, and that will necessitate some changes.
Forge Upgrade Timeline
The Forge Upgrade will be incremental in phases. This upgrade starts February 2026 and will complete in April 2026.
|
Phase |
Status |
Description |
|---|---|---|
|
1 |
In progress |
Technical uplift of eSign service infrastructure to support Forge. No user impact. |
|
2 |
Pending |
Atlassian Marketplace converts the eSign listing from Connect to Forge. Existing installations will be slowly updated.
|
|
3 |
in development |
Incrementally eSign front end pages/screens will be replaced with equivalent Forge pages. |
Forge Changes and Impacts
This table will serve is a reference to the changes and impact the users will see in the new Forge platform.
|
Feature |
Impact |
Change Comments |
|---|---|---|
|
Jira Mobile App |
High |
Atlassian Forge does not support the Atlassian Jira mobile app. Users will no longer be able to execute Signatures within the mobile app. |
|
Signature Profile page location |
Low |
Atlassian Forge has removed the option to add links to the User Profile menu. The Signature Profile page, used to manage and reset Pins will move. New location is TBD. |
|
User Time Zone |
Low |
Atlassian Forge retrieves the time zone from the user’s browser instead of the Jira user profile. This may affect users with a different time zone settings between Jira and their PC/browser. |
|
|
|
|