Contents
The Decline To Sign feature allows invited users to respond to a signature request with a Decline Reason and optional comment. For example, an invitee may decline to sign with the reason “Changes Required” and add a list of changes in the comment.
The status and reason for the decline is displayed in the signature panel. Once the blockers have been resolved, the user can proceed to Sign normally.
Decline Flow
Users invited to sign can start the Decline flow from the Sign button dropdown menu in the Signature Panel.
In the decline dialog, a user can enter the Meaning, Reason and an optional comment.
After declining, the status of the pending invite will change to Declined and the Decline Reason will be displayed to all users.
If a comment was added in the decline dialog, eSign will post what was entered into a new comment on the work item. Jira Notification rules on new comments can be used to notify watchers or other team members.
The Decline to Sign event is added to the Audit Trail.
Options After Declining
If a user Declines to Sign, they can later return to the same signature request and apply a signature once whatever factors they were waiting on have been resolved.
Users are also able to apply a second decline after the first if new factors are discovered.
Note, however, that users cannot directly Decline a completed Signature.
Notification
Jira Notification rules on new comments can be used to notify watchers or other team members when Declines are recorded with comments.
There is a “Decline Event” webhook also available to trigger a Jira automation rule on Decline.
Configuration
This feature is enabled and configured in eSign Project Settings.
Notes
-
For eSign validators (e.g. Required Signatures) and other business rules, declined invites are considered Pending Signatures.