Electronic Signatures

by AppfireAtlassianPaid

Adds credential validation and electronic signature history to Jira issue workflows.

Facts verified marketplace.atlassian.comAd-free rankings
PRICINGPaid
DEPLOYMENTCloud · Data Center · Server
CATEGORYAdministrative tools
UPDATED ON MARKETPLACE
Electronic Signatures — screenshot from the Atlassian Marketplace listing

What it does

Electronic Signatures adds custom fields for validating credentials when editing Jira issues. It supports validation of a system user's username and password, or the password of the currently logged-in user. A separate issue tab displays signature history, and tickets can be filtered by signing users. The vendor states that the app complies with 21 CFR Part 11.

Key capabilities

from the Atlassian Marketplace listing

User credential validation

The User Validator Field checks a system user's username and password.

Logged-user validation

The Logged User Validator Field checks the password of the currently logged-in user.

Signature history

The issue tab panel displays information about signatures recorded on an issue.

Signer filtering

Search can filter tickets by the users who signed them.

How it compares

Electronic Signatures is a paid Jira add-in available on data center, cloud, and server. Electronic Signature for Jira is also paid and supports data center and server, while BeyondTrust Privileged Remote Access Integration for Jira is paid and supports cloud.

NamePricingDeploymentUpdated
Electronic Signaturesthis pluginPaidCloud · Data Center · Server
Electronic Signature for JiraPaidData Center · Server
BeyondTrust Privileged Remote Access Integration for JiraPaidCloud

In the catalog

1,002 plugins in Jira · Administrative tools

Price distribution: 271 free, 275 freemium, 456 paid

Pricing & deployment

Platform
Atlassian
Product
Jira
Deployment
Cloud · Data Center · Server
Pricing
Paid

More from Appfire

Similar plugins in Jira · Administrative tools

View all 1,002 →

What the vendor says

«Electronic Signature Fields app contains custom fields for checking user credentials and is compliant with 21 CFR Part 11. This means that the user needs to enter valid credentials when editing a ticket. This prevents unauthorized actions on issues. You can check user credentials according to the required technical …»

Official marketplace listing

Publisher
Appfire
Updated on marketplace
Facts verified

Tags

compliancerisk managementuser permissionsworkflow