2026 Change Log

IMPROVED
UX

Improved signing workflow with new inline Sign Here actions in the Signature panel.
Previously, users clicked the top Sign button, selected a signature type, and entered their pin.
Now, users with open Invites can sign directly from their assigned row via a labeled button (for example, “QA Approval”), reducing clicks and making the target signature type explicit.
The inline Sign Here also includes the Decline to Sign drop down action if enabled for the project.
Note: The Sign button in the primary toolbar is still available and can still be used even if the new Sign Here button is available.

FEATURE
NEW

Sequential Signature support is now available. With this feature enabled, pending signatures must be completed in order. e.g. If three users are invited to sign for #1 Dev Approval, #2 Product Approval, #3 QA Approval with Sequential signatures enabled, the Dev Approval must be completed first before #2 and #3 can be signed. The upcoming signatures will show a status of “Queued” in the Signature Dialog.

This feature is opt in and will only apply to spaces/projects with Sequential Signatures enabled. In this case, a “Sequential” label will be displayed in the Signatures panel footer.

FEATURE
UX

Auto Finalize
eSign has a new feature to enable automatic finalize of Signature pages once all pending signatures have been completed.

This can streamline workflow and user experience by immediately locking down signatures once all required invites are resolved. This can simplify automation integration as now the Finalize webhook will trigger once on completion of all signatures. It also works with the expanded Notification on Finalize feature for teams that want eSign to directly notify the team once all signatures are done.

Enable this feature in the eSign Space Settings page.

IMPROVED
UX

This release introduces Enhanced Email Notification, as it is now possible to email signature participants on on Invite, Signature (Execute), Decline and/or Finalize. Previously eSign could only natively notify on Invite. Customers that needed more extensive notifications needed to utilize webhook automation scripts.

If enabled, the signature participants will receive email notifications directly and immediately from eSign when the event triggers. Each event can be individually enabled and configured per Jira space.

Enable and configure enhanced notifications in the new Notifications section of the eSign Space Settings page.

FEATURE
UX

The PDF Signature Archive Report may now be generated and downloaded on demand. Previously this report was only generated and attached on manual or automated workflow Finalize of signatures.

This new access allows easier adhoc generation of this report at any time for work items with signature data. Access the report from the Signatures Panel > Reports > Archive menu in the Work Item view.

IMPROVED

This release improves email control and visibility:

1. The JSM Portal now display the signee email alongside signer name, title, and signature type so Signature records clearly show who signed, especially for external users whose names may be ambiguous.

2. Customers with specific privacy restrictions on email can now opt out of capturing user email as part of executed signatures. This takes effect immediately on a go forward basis. Note that users will still receive emails from eSign for notifications and pin resets.

NEW
API

Import Signatures API
We added a secure, token-protected Import Signatures API using a standardized JSON format. This expands on the legacy CSV import path and enables reliable import of externally captured signatures into Jira work items and eSign.
Common use cases include data migration, offline capture synchronization, and third-party transactional integrations.

See External Integration API | Import Signatures [POST]

IMPROVED
WORKFLOW

The Required Signatures Validator extended for Signature Types.
The validator can now be configured with a Signature Type(s) selector instead of a single group picker, allowing teams to verify that one or more specific signature types have been captured before workflow transition.
This creates clearer, audit-friendly rules and supports broader scenarios with fewer validators, since a single rule can now enforce multiple required signature types.
When signature types are role-restricted, this also preserves the intent of group-based controls while adding flexibility and reducing configuration complexity.

IMPROVED
WORKFLOW

For improved integration options, the eSign Webhook Event payloads can now optionally include the signee and invitee email addresses. This can be helpful where an automation flow needs to connect with signature participants. For example custom notification via email or a third party service that uses email as an identifier. Email inclusion is off by default; it can be enabled by an administrator at the eSign app configuration level.
eSign Webhooks are linked to Jira Automation flow web triggers in the eSign Space Settings page for the following events: Invite, Execute (Sign), Decline, and Finalize.

IMPROVED
UX

Improved Signatures Panel live updates: the panel now auto-refreshes when signatures are changed by other users or background workflow automation.

Previously, the panel refreshed after actions taken by the current user, but updates from other actors required a manual refresh. With this enhancement, changes such as workflow-triggered automatic invites and external signature updates appear automatically, giving users a more real-time and reliable view of signature status.

UX

Additional UX Changes

• The Signature Panel toolbar layout has been slightly updated to promote the Signature Admin to the top level and group reports into a single drop down.

• eSign will wow show a notification to users on work items where the Signature Panel is hidden but there is signature metadata. This is a workaround for a known limitation of the new Forge platform.

• The limits on the Invite to Sign and Execute Signature dialogs can now display up to 18 different Signature Types.

• For consistency between configuration and operations, the phrase Signature Meaning has been renamed to Signature Type in the eSign Screens and dialogs.

• In workflow configuration, the term “post functions” has been changed to workflow actions to align with Jira’s revised terminology.

• eSign email templates had slight layout and formatting improvements.

WORKFLOW

The workflow Admin Action > Void now reopens if required.

The eSign Admin action > Void signatures will now automatically reopen signatures when triggered against a Finalized work item. This enhancement will simplify the typical workflow where the work item is returned to an early state for rework and existing captured signatures need to be voided so new signatures can be captured.

The Signature Audit trail will record if the signatures were reopened during the workflow action in addition to voiding.

TECH

Improved Email Recovery

When a user requests a PIN reset, we now automatically attempt to restore delivery for addresses that were previously suppressed after a bounce event. This helps users recover faster after temporary mail server issues or mailbox blocks, reducing support delays and missed reset emails.

TECH

Library dependency and security updates

FIXED

• Resolved an issue with the Invite workflow action (post-function) where it failed to invite users in the assignee/reporter built-in Jira fields after a recent Jira payload change

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

FORGE 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

FORGE 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.

UX

FORGE The Cancel Invite, Cancel Assignment and Void Signature context menu confirmations were moved into a separate popup to prevent clipping within the Signature panel. (2026-06-11)

PATCH

FORGE Patch 2026-06-17:
- Fixed pin reset email link to Signature Profile updated for eSign on Forge path
- Fixed issue with Signature Invite post functions not being able to read target users listed in custom fields if not included in Jira webhook payload
- Improved forge migration that automatically pins the Signature panel visible to work reliably for customers with more than 100 signature projects. Added manual bulk pin option to the eSign App Diagnostics page.

INFO

The eSign app has been renamed to eSign Signatures for Jira. This change will be visible inside app administration and will also affect the app account name which is visible in work item comments. (2026-06-17)

FIX

FORGE Fix an issue where the imported signature date and times were not displayed in the new Signature Panel (2026-06-20)

FIX

Fix an authorization 401 error contacting the Jira API to fetch extended change logs for issues with over 100 history entries and signature verification enabled for custom fields. (2026-07-07)

FIX

FORGE Fix an issue where the esign aggregate custom fields (e.g. Signature Count) were not updating automatically after signatures. (2026-07-09)

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.