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 Hub
With the Forge version a new centralized dashboard for Signature information is available under the primary Confluence Apps menu. This page expands on the previous Search only page by introducing a My Invites and My Signatures panel, plus access to the user’s Signature Profile, and eSign News and User Guide.

There is also a similar Signature Dashboard for each Space.

IMPROVED

PDF Export has been improved to match the on screen rendering of Signature Tags and Blocks, including the specific cursive font used for Signatures.

The Search Macro can now also be exported to PDF.

TECH

Technical and infrastructure updates to prepare for Atlassian (US) Government Cloud and FedRAMP platform support. This includes a new isolated signature processing service, hosted within the US by a SOC2 compliant provider. See Atlassian Government Cloud | Atlassian for more information.

FIX

Resolved a locking issue where the a signature retry could not be completed within 15 seconds after entering the pin incorrectly. (2026-02-12)

FIX

Applied stale byline context workaround - Confluence may incorrectly pass the previous page's content ID to app dialogs after in-page navigation (known Atlassian platform issue ECO-1349). eSign now cross-checks the dialog context against the actual browser page URL and corrects the ID when a mismatch is detected. (2026-03-05)

FIX

Resolved issue with Starting signatures that affected a subset of pages authored with the legacy Confluence editor. (2026-03-16)

UX

As a Technical update there are no changes to features or functionality that will impact end users.

TECH

Atlassian Forge Compatibility - We are upgrading to the new Atlassian Forge platform this year. This initial technical update will enable phase 1 compatibility. There will be no visible changes to the application, but please let us know if you encounter any issues.

TECH

Concurrent Signature Support - The Signature infrastructure has been enhanced to allow multiple signatures to be securely captured even if they are executed at the exact same time. Previously the second user would have to retry their signature.

TECH

Technical Library and Security Updates - Dependent libraries have been updated for security.

TECH

Email Notification Changes - The automated email infrastructure (e.g. pin resets and signature invites) has been updated. Users may notice slight differences to the email formatting.

FIX

Correct an issue where space administrator’s override privileges were not detected to perform Signature Administration on non-owned pages. (2026-01-29)