See https://support.esign-app.com for eSign Documentation and Support
eSign for Jira - 2023 Q1 Updates
 | eSign for Jira |
Contents
Signature Issue Type Restrictions and Meanings
It is now possible to choose which Issue Types (e.g. Epic, Enhancement, Task) in a project can have Signatures, and for each of those Issue Types configure an individual list of signature meanings (e.g. Dev Approval, QA Approval, Compliance Review).
Combining this option with Jira Issue Type specific workflows and eSign validators and post functions can allow customers to have very different approval paths for each issue type.
The Issue Type specific meanings are displayed in the Execute Signature , Invite Pages, as well as the bulk Sign/Invite options.
Configure the Issue Type restrictions in the eSign Project Settings page.
Extended Signature Verification for Built-in and Custom Issue Fields
In response to customer requests, we are please to announce that eSign for Jira has added support for Extended Signature Verification. With this enhancement, eSign can be configured to verify additional Jira built-in and/or custom fields have not been modified since signing.
In default field verification mode, captured signatures are checked against the issue Summary, Description, and Attachments. Now additional fields can be included with the signature verification. The issue history is searched for changes to any additional fields after a signature.
Globally Enable or Disable Signatures for all projects
For customers that have many Jira projects it is now possible to disable eSign for all projects, and selectively enable it for projects that require Signatures. Find this new option under Apps | eSign App Settings.
The eSign Project Settings page has been updated to make it clear what global setting is in place.