The Atlassian Marketplace and Developer ecosystem is evolving from Connect Apps to Forge Apps. To align with Atlassian guidance and receive the benefits of improved support, reliability and security, eSign for Jira is migrating to the Forge platfrom in 2026.
What this means to existing eSign Customers and Users:
-
The overall signature experience and data are unchanged; eSign is providing the same features you are used to.
-
The signature data storage is not changing. All of your data will continue to be stored within your Atlassian Jira cloud site.
-
eSign on Forge will be initially released as “opt-in”; your site will not receive the update until the Jira Administrator updates the eSign app.
-
Because it is a foundational platform and technology change, we recommend that you test to ensure that your specific configuration and workflows work well, and identify where there may be some user/training impact due to the changes.
Forge Upgrade Timeline
The Forge Upgrade will proceed in phases.
|
Phase |
Description |
|---|---|
|
1. Infrastructure
|
The eSign backend service infrastructure is upgraded to support Forge platform technology. No user impact for this phase. |
|
2. Early Access
|
The new version will be released for optional update. Existing customers will not be automatically upgraded. This version may be installed in sandbox/test sites and updated to production on a per site basis during the Early Access phase. Updates to the Forge release are one-way and cannot be rolled back. We recommend testing in a sandbox or non-production environment first. Once the Early Access phase has started all new installations will be eSign on Forge. |
|
3. Full Release
|
After eSign on Forge has proven stable, it will transition to Full Release and will be automatically rolled out to the remaining sites. |
eSign Feature Changes
This section highlights the various eSign user accessible features and any functional impacts of the forge upgrade. This list may be useful in reviewing your team's usage of eSign and identifying the scope of use cases to test.
|
Feature / Page |
Impact |
What’s Changed |
|---|---|---|
Signature Process
|
|
|
|
Signature Panel (Work Items) |
Low |
Signature date and times are shown in the current user’s time zone The panel will display for all work items in Spaces with Signatures enabled |
|
Execute Signature |
no change |
|
|
Invite to Sign |
Low |
Pending checkbox renamed to Unassigned |
|
Decline to Sign |
no change |
|
|
Finalize (and Archive) |
Low |
Preview link for the PDF signature archive is not available |
|
Verification Report |
no change |
|
|
Signature Admin |
no change |
|
|
Signature Audit (tab) |
no change |
|
Signature Management
|
||
|
Signature Hub |
Low |
The new Signature Hub is available under the global Apps menu. It provides a dashboard of signature rollup information, plus links to the user Signature Profile, eSign News and User Guide. |
|
Signature Profile |
Low |
The Signature Profile page can be reached from the Signature Hub, Signature Panel, the Service Request Management portal, and the Jira Personal Settings > General Settings. The Signature Profile is not accessible from the Jira User Profile menu as that is not supported by Forge. |
|
|
|
|
Jira Service Management
|
||
|
Service Request Signatures (Service Portal) |
MEDIUM |
The Signatures panel is now displayed below the Activity section of the Service Portal. Atlassian Forge does not support the previous location (above the Activity section). Also, the Service Management capabilities have been extended so that external unlicensed users can use Signature Pins and Decline to Sign. See the change log for more details. |
|
|
|
|
Bulk Operations
|
|
|
|
Bulk Execute |
no change |
|
|
Bulk Invite |
no change |
|
|
Bulk Verify |
Low |
The bulk verify report supports up to 50 work items per operation. |
|
Export Certificates |
Low |
Direct export from the Jira search request view is not supported on Forge. The same report is available from Bulk Signature Operations using Bulk Verify. |
|
|
|
|
Administration
|
|
|
|
Space Settings |
Low |
Space configuration is now in Space Settings > Apps > eSign Electronic Signatures. |
|
App Administration |
Low |
Site administration is now under “eSign Electronic Signatures” within Jira > Apps > Manage Apps. For Administrators, the Apps > Signature Hub > … > App Settings provides a shortcut to access eSign App Administration. |
|
App Settings |
Low |
API Token management has been moved to its own page. Additional Customer Pin settings available |
|
API Tokens |
Low |
|
|
Administration Audit |
no change |
|
|
Quick Start |
no change |
|
|
Import Signatures |
no change |
|
|
Transfer Signatures |
Low |
Admin page renamed from Copy to Transfer to align with Atlassian data transfer plans. |
|
|
|
|
Workflow Automation
|
||
|
Current User Signee Rule (Validator) |
no change |
|
|
Required Signatures Rule (Validator) |
no change |
|
|
Create Pending Unassigned Action (Post Function) |
no change |
|
|
Invite Signatures Action (Post Function) |
no change |
|
|
Finalize Signatures Action (Post Function) |
no change |
|
|
Reopen Signatures Action (Post Function) |
no change |
|
|
Admin Action (Post Function) |
no change |
|
|
|
|
|
Additional Items
|
|
|
|
eSign Custom Fields |
no change |
All custom eSign read-only fields will transition to Forge automatically: Signature Export, Signatures Finalized, Signature Pending, Signed On, Signature Count, Signed By, Signature Status Count |
|
eSign Space Permissions |
no change |
There are no changes to fine-grained permissions used with Advanced Security. Existing grants will transition to the Forge version of these permissions automatically: eSign Execute, eSign Finalize, eSign Invite, eSign Manage, eSign Administer |
|
External API |
no change |
|
|
Jira Mobile App Support |
HIGH |
Atlassian Forge does not yet support the Jira Mobile App. Because of that, eSign will not be available within Jira Mobile.
|
References
For more information about the Atlassian Forge platform and transition, see: