---
title: "ES - Configuring electronic signature"
canonical: "https://support.appfire.com/space/ESF/17498300/ES%20-%20Configuring%20electronic%20signature"
format: markdown
---
> Macro (aura-html)

## Configuring Electronic Signatures 

> ℹ️ <span style="color: #333333">Migration between Server or Data Center instances is available starting with version 3.1.2-jira8 and above using </span>[Configuration Manager for Jira](https://marketplace.atlassian.com/apps/1211611/configuration-manager-for-jira?hosting=server&tab=overview)<span style="color: #333333"> app. Use </span>[Project Snapshot](https://appfire.atlassian.net/wiki/spaces/CMJ/pages/82779727)<span style="color: #333333"> to migrate Electronic Signatures history, Logged User Validator and User validator custom fields, validator and post function, and </span>[System Snapshot ](https://appfire.atlassian.net/wiki/spaces/CMJ/pages/82777327)<span style="color: #333333">to migrate Electronic Signatures Configuration page.</span>


The following settings are optional but give you flexibility and enable you to change credentials validation rules.

1. Go to Jira **Administration →  Manage Apps → Electronic Signatures → Configuration. **  
  
> Macro (inline-media-image)

  
  
> Macro (inline-media-image)
2. Set up your '**Username** check' **sensitivity** and **Maximum invalid login attempts, **<span style="color: #333333">opt how to display </span><span style="color: #333333">**Validation error message**</span><span style="color: #333333"> as a popup message or on the transition screen</span>.
  
3. Starting with version 3.0.0 you can use **[ES validator](https://appfire.atlassian.net/wiki/display/CADS/ESF+-+Requesting+specific+group+or+user+to+sign)** 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. | [approvals@appfire.com](mailto:approvals@appfire.com) |
| 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},  
This is to let you know, <a href="$issueWebLink">$issueKey</a> transition change requires your approval.  
Please approve!   
Regards, |
| 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<br>> ℹ️ The feature is available starting with 3.0.1 version. | If multiple validators are set up on different transitions the setting will be applied to all transitions. |

  


5. <span style="color: #333333">Starting with version 3.0.2 for Jira 8 and above you may use </span><span style="color: #333333">**Password autocomplete**</span><span style="color: #333333"> which enables to paste password within ES password field. Kindly note that this action is not recommended by Title 21 CFR.</span>

6. Starting with version 3.0.4 you are able to set up **[ES post function](https://appfire.atlassian.net/wiki/spaces/ESF/pages/17498200/ES+-+Requesting+specific+group+or+user+to+sign#ES-Requestingspecificgrouporusertosign-Addingapostfunctiontoatransition)** to notify signatories that their signature is required before the issue achieves a particular state.

7. <span style="color: #333333">Starting with version 3.0.6 you may select how to display Electronic Signatures tab (</span><span style="color: #333333">*prev. Issue Sign Information tab*</span><span style="color: #333333">) in a ticket. It's possible to place it separately or as a part of the Activity tab.</span>

|  |  |
| --- | --- |
| ![image](media://f6dfe907-9ce4-462e-93ee-5f15b805d53d) | ![image](media://51eb017b-b358-42fe-9dd1-840b730d7987) |

<span style="color: #333333">8. If you want to retain the value in the Electronic Signatures fields during bulk moving tickets between projects, mark </span><span style="color: #333333">**Issue actions**</span><span style="color: #333333"> checkbox on the configuration. This feature is available starting with version 3.0.8-jira8 and above.</span>

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 <span style="color: #6b778c">to render sign datetime info inside of Esf Signature Info Tab</span>.

11. Set rendition to render Email body in <span style="color: #6b778c">**Email frequency**</span>. 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

## What's next?

[ES - Requesting specific group or user to sign](https://appfire.atlassian.net/wiki/spaces/ESF/pages/17498200)