| Table of Contents | ||||
|---|---|---|---|---|
|
Adding electronic signature fields to the issue
Electronic Signature Fields app contains the following custom fields for signing tickets:
- Logged User Validator Field - validates username and password of a system user according to Title 21 CFR 11.
- User Validator Field - validates password of a currently logged in user according to Title 21 CFR 11.
To configure the User Validator or Logged User Validator field, perform the following steps:
...
As a result, you will have the electronic signature field on the selected screens, and users will have to enter valid credentials when editing tickets.
...
Locking signatures after a number of failed login attempts
| Info |
|---|
This feature is available starting with version 2.0.1 for Jira 8 and above. |
...
That's it. Electronic Signature field will now be validated according to selected settings.
Configuring JQL functions
The following custom JQL functions enable you to expand your search in Jira:
- issue in signedIssues() - returns all signed tasks.
signedIssues()
signedIssues(‘project’, ‘Project name’)
signedIssues(‘project’, ‘Project name’, ‘>’, ‘date’)
signedIssues(‘user’, ‘jdoe’)
signedIssues(‘>’, ‘date’)
- issue in unsignedIssues(Project name) - returns all unassigned tasks from Project X.
...
What's next?
...
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.
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. | approvals@cprime.io | ||
| 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 Electonic 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.
That's it. Electronic Signatures are now set up.