Apps documentation
Electronic Signature for Jira
Electronic Signature for Jira
Release notes
Last updated Sep 3, 2021


Electronic Signature for Jira
Electronic Signature for Jira

Electronic Signature gives you the ability to authenticate users when they perform various activities in Jira. A special custom field requires users to provide their username and password in order to sign off an issue creation, editing, or transition. This way, you can build approval processes compliant with the FDA regulation CFR 21 part 11.

21 CFR Part 11 is the part of Title 21 of the Code of Federal Regulations that establishes the United States Food and Drug Administration (FDA) regulations on electronic records and electronic signatures (ERES). Part 11, as it is commonly called, defines the criteria under which electronic records and electronic signatures are considered trustworthy, reliable, and equivalent to paper records (Title 21 CFR Part 11 Section 11.1 (a)).

Key features

With Electronic Signature you can:

  • enable user authentication in a custom field on the Create issue screen, Edit screen, and upon workflow transitions
  • select user groups authorized to submit an electronic signature in particular projects
  • display a history of transitions and their authors in a dedicated panel
  • monitor failed authentication attempts in automatically generated logs
  • lock transitions after failed authentication
  • specify a number of failed authentication attempts, after which a transition is locked
  • track access attempts and export them as PDF reports
  • display PDF reports as attachments or external comments on the Customer portal
  • select what data is included in the reports
  • automatically attach PDF reports to their issues of origin

The app doesn’t store any passwords. Only usernames are saved in the PDF reports.


Find Electronic Signature for Jira on the Atlassian Marketplace.

Additional information

To further enhance your Jira experience, check out: