2026 Change Log

PLATFORM

Atlassian Government Cloud

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

See Now Available on Atlassian Government Cloud | Digital Rose for more information.

improve

Release Log added to Audit Trail

The Document Release event log is now saved as part of the document record and included in each Release Copy’s Audit Record report. This allows historical review of the release events.

improve

Automation webhook payload extended

The Automation webhook payload now includes the user email address (in addition to name and account ID) for document signature events (Review Approval and Training Completion). This will improve integration options for customers. See Webhook Automation for more information about the integration events that eSign Documents can publish.

UX

Fewer Review Approval Notifications

For a document that is under review by multiple users, eSign Documents was sending email notification to the next reviewer after the previous reviewer signed. This is changed and now the next reviewer will only receive notification for Sequential reviewed documents.
This change only affects reviewer notifications. The Document Owners will continue to be notified of approvals. See User Notifications for the list of notification rules.

UX

Custom Document ID constraints applied

By default eSign Documents can generate an automatic Document ID (e.g. SOP123). Customers with specific document naming policies or pre-existing documents can apply custom Document IDs when starting documents/revisions.
To prevent issues with Confluence searches and indexing, special characters are now excluded. Custom Document IDs support up to 25 characters, using letters (A–Z, a–z), numbers (0–9), and separator characters (period, colon, hyphen, underscore).

FIX

To mitigate a known Confluence byline issue, eSign now validates that the current page URL matches the page identifier provided by Confluence. In some navigation scenarios, Confluence may display byline items from a different page and pass an incorrect page identifier to apps. Without this validation, actions could be attempted against a page other than the one currently displayed. If a mismatch is detected, eSign blocks the action and prompts the user to refresh the page or use the eSign Document Header.

For details on the platform issue, see: https://jira.atlassian.com/browse/ECO-1349

PLATFORM

Forge Compatibility Updates

Behind the scenes, the eSign platform received several updates to position for the upcoming Forge platform transition.

PLATFORM

Security and maintenance updates for third-party libraries.

UX

Raise the limit on maximum review approvals per document type to 18. The previous limit was 12.

UX

Adjusted the optional reviewer rows to be easier to enable in the Assign Reviewers dialog.

FIX

Resolve issue where security controls would prevent document owners from Returning to Draft if the “Owners as Admins” option was disabled for space.

FIX

Applied technical workaround to refresh stale bylines - Confluence may incorrectly display a previous page’s byline text after in-page navigation (known Atlassian platform issue ECO-1349). eSign now cross-checks the dialog context against the actual browser page URL and forces a byline refresh and corrects the text when a mismatch is detected. (2026-03-05)

FIX

Correct swapped heading labels for the default training and periodic review intervals in the doc type settings page. (2026-03-11)

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 enable phase 1 Forge compatibility. There will be no visible changes to the application, but please let us know if you encounter any issues.