2026 Change Log

platform

eSign transition to the Atlassian Forge platform.

What this means to existing eSign Customers and Users:

• The overall signature experience is not changing; 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.

• We recommend customers with complex Signature workflows test this new version in a separate test site prior to upgrading in production.

See eSign for Jira - Forge Upgrade FAQ for more details and detailed feature impacts.

FEATURE

Signature Pins are now available for external customer users. When this feature is enabled, customer users will be required to enter a signature pin to apply a signature, the same way internal users do.
This change is for compliance environments that require additional verification for external user signatures.
Customer Signature Pins can be reset via email and updated.

FEATURE

Decline to Sign is now available in the Signature management portal. Both internal users and customer users that have been invited to sign can elect to “Decline” the signature providing a reason and optional comment.

As part of this change, eSign app comments will also be visible in the Signature management portal to make them visible to external customer users.

NEW FEATURE

Customer Signature Types for JSM

eSign for Jira Service Management now supports multiple Customer Signature Types, giving you more targeted control over external signature requests.

• Define and customize multiple Signature Types for external Customer users. Instead of just “Customer Approval”, set up targeted signature names like “Requisition Approved”, “Support Authorized”, or “Contract Verified”.

• Just like internal Signatures, control and limit Customer Signature Types by Work Type, Request Type, Status and Category. Enable the right signatures at the right time for the right service requests at the desired status.

• Customers (Reporters/Participants) can be invited to Sign for specific Signature Types through the regular Invite dialog, and through Jira workflow automation.

• Customer users will now see the Meaning field in the signature dialog. This is consistent with internal users, and provides clarity on the purpose of the signature.

Configuration for the new Customer Signature Types are available in eSign Project Settings.

No changes are necessary for existing JSM projects. Customer users will continue to have access to the default “Customer Approval” signature type.

PLATFORM

Atlassian Government Cloud

eSign infrastructure and security has been updated to support deployment of the app to the Atlassian Government Cloud | Atlassian.

eSign will soon be available for installation in the AGC marketplace.

UX

Improve the layout and resizing of the Signature dialog to facilitate Signing on small screen devices.

TECH

Security and Technical updates for external libraries.

FIX

Update the eSign Invite workflow post function configuration to support Jira groups with names containing special html characters like '&'.

FIX

Resolved issue where requests/work items in JSM projects without a Request Type in JSM spaces could not be signed. (Mar 16, 2026)

UX

Hide the default “Customer Approval” signature type from the Invite dialog where it appeared in non-JSM spaces in certain configurations. (Mar 25, 2026)

TECH

Atlassian Forge Compatibility - This update is Phase 1 of the transition to the new Atlassian Forge platform.

This stage has no visible changes for the user community, but please let us know if you encounter any issues.

See the eSign for Jira - Forge Upgrade FAQ for more information on this upgrade.

TECH

Improve job queuing for Invite/Pending signature post functions. This will improve scalability so that very large work volumes (e.g. 1000+ items) can be processed without being blocked by the Atlassian API rate limiter.

UX

The Signature Invite emails have been updated to include the Space Name for additional clarity to invitees.