Workflows

It is possible to integrate eSign with Jira workflows through advanced workflow configuration.

Required Signatures Validator

The eSign addon includes a custom workflow Validator that can be leveraged to control workflow. It can be used to require a certain number of signatures in the current status (or total) before a transition to the next status is allowed.

Add the eSign: Signatures Required validator in the desired transition using the Jira workflow editor:

Select the minimum number of signatures required and indicate if current status or any status.

Reset Signatures Post Function

There is an optional post function that can be enabled in Jira to automatically clear signatures from an issue. This could be used to reset/restart signatures based on a specific workflow transition. To enable this, add the eSign: Reset Signatures post function to the appropriate transition(s) in the workflow.

Prevent Signature Changes on Closed Issues,

To sign an issue, the user must have view access to the issue and the issue must be editable (unless the Advanced Security option is enabled). When an issue is closed, it is possible to prevent new signatures by setting the issue to be read-only through workflow status property jira.issue.editable=false.
See this link for more information: https://confluence.atlassian.com/jirakb/issues-are-editable-in-closed-state-218268664.html

Addon Issue Fields

The eSign addon includes and automatically populates read-only issue fields Signature Count, Signature Export, Signed By and Signed On. These can be used to enhance search and filter capabilities to locate Jira issues with signatures. Enable these fields within Jira Issue Configuration - Custom Fields, and then add to appropriate screens.

These custom fields can also be included Jira filters, exports, and third party apps like Xporter.