Configuring Electronic Signatures
This page describes how you can configure the Electronic Signatures app for the versions 3.0 and above. The documentation for the previous versions can be found here.
| Info |
|---|
Migration between Server or Data Center instances is available starting with version 3.1.2-jira8 and above using Configuration Manager for Jira app app. Use Use Project Snapshot to to migrate Electronic Signatures history, Logged User Validator and User validator custom fields, validator and post function, and and System Snapshot Snapshot to migrate Electronic Signatures Configuration page. |
The following settings are optional but give you flexibility and enable you to change credentials validation rules.
Go to Jira Administration → Manage Apps
...
→ Electronic Signatures → Configuration.
...
Set up your 'Username check' sensitivity and Maximum invalid login attempts, opt how to display Validation error message as a popup message or on the transition screen.
Info This feature is available starting with version 2.0.1 for Jira 8 and above. The ability to select displaying of Validation error message is available starting with 3.0.3 version.
Starting with version 3.0.0 you can use ES validator to request several signatures on Issue transition by notifying users via email. Specify how this email should look like for the approver(s):
Field | Description | Example |
|---|---|---|
Email from address | The default address the Jira server will use to send emails from. This should be an allowed by your SMTP server email address. |
...
...
Email subject | The subject for the email. | Please approve status change on ${issueKey} | ||
Email template | The email body the approver(s) will receive. | Dear ${signee.displayName}, | ||
Email frequency | This checkbox enables you to send emails to required approvers only on the first try to make an Issue transition with ES validator
| If multiple validators are set up on different transitions the setting will be applied to all transitions. |
5. Starting with version 3.0.2 for Jira 8 and above you may use Password autocomplete which enables to paste password within ES password field. Kindly note that this action is not recommended by Title 21 CFR.
6. Starting with version 3.0.4 you are able to set up ES post function to notify signatories that their signature is required before the issue achieves a particular state.
7. Starting with version 3.0.6 you may select how to display
...
Electronic Signatures tab (prev. Issue Sign Information tab)
...
in a ticket. It's possible to place it separately or as a part of the Activity tab.
 |
 |
8. If you want to retain the value in the Electronic Signatures fields during bulk moving tickets between projects, mark Issue actions checkbox on the configuration. This feature is available starting with version 3.0.8-jira8 and above.
In addition, you can specify the Project roles field. Users from these groups are not committed to enter password on Issue editing screen.
9. Set Use
...
Jira default
...
datetime format if you want to render sign datetime info inside of
...
ESF Signature Info Tab in short format. Otherwise will be used full
...
datetime format.
10. Use Custom datetime format to specify custom datetime format. It will be used to to
...
render sign datetime info
...
inside of Esf Signature Info Tab.
11. Set rendition to render Email body in Email frequency. By default it equals to Plain Text. Or you can set HTML rendition.
12. Allow bulk sign-up option turn on custom bulk sign of issues. Based on JQL. When set up, Jira navigation bar contains new Sign item.
13. Turn off E-mail notifications from ES Issue Validator - use it if you do not need E-mail notification from ESF validators and postfunctions