See https://support.esign-app.com for eSign Documentation and Support
eSign for Jira - February 2022 Update
1. Service Management Portal now supports internal user signatures
The eSign functionality has been extended within Jira Service Management to allow full Atlassian user accounts to sign service requests within the portal, in addition to external customer users.
This enhancement introduces the following changes.
As before, customer accounts (customers) may sign service requests with an assertion checkbox.
Atlassian User accounts (users) may now view and sign requests within portal.
Users will be required to enter a Signature Pin and Meaning to sign.
Users/Customers with access to a Service Request will see all signatures on that request.
The eSign User Profile page is now available in the JSM Portal to allow Users to set or reset their Pin.
Users/Customers may only sign each request once within the Portal.
See https://support.atlassian.com/atlassian-account/docs/what-is-an-atlassian-account/ for more information on the difference between Atlassian accounts and Service Management customers.
2. Signature Meanings Extended
The limits on Signature Meanings have been raised.
Each project can configure up to 15 distinct signature Meanings
Each Meaning having a maximum length of 24 characters.
The length of the Meaning pick lists in the Execute Signature (sign single issue) and Bulk Execute (sign multiple issues at once) have been extended to show the longer meanings.
3. Faster Finalize with PDF Archiving
PDF Signature Archiving has been moved to background processing so that users do not have to wait for the PDF archive during the Finalize. Now after the Finalize is complete the Signature Archive process will start. Archiving will usually complete in less than 30 seconds.
4. Other Items
eSign User Settings page renamed to eSign User Profile to align with Atlassian User Profile conventions.
Minor UX updates for branding