Build in electronic signatures compliant with 21 CFR Part 11 into your compliance workflow with custom field validation use cases
Build in electronic signatures compliant with 21 CFR Part 11 into your compliance workflow with custom field validation use cases
Build in electronic signatures compliant with 21 CFR Part 11 into your compliance workflow with custom field validation use cases
User Validator Field
Logged User Validator Field
Ticket Signatures Information
This field validates username and password of a system user according to 21 CFR 11.
This field validates a password of a currently logged in user.
You can view all issue signatures information in a separate tab.
User Validator Field
Logged User Validator Field
Ticket Signatures Information
This field validates username and password of a system user according to 21 CFR 11.
This field validates a password of a currently logged in user.
You can view all issue signatures information in a separate tab.
More details
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 elements of 21 CFR Part 11 that defines the criteria under which electronic records and electronic signatures are considered trustworthy, reliable, and equivalent to paper records.
Key features
- User Validator Field - validates username and password of a system user
- Logged User Validator Field - validates a password of a currently logged in user
- Issue Signs Information - issue tab panel with the history of the signatures
- Search - you can filter tickets by users who signed.
More details
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 elements of 21 CFR Part 11 that defines the criteria under which electronic records and electronic signatures are considered trustworthy, reliable, and equivalent to paper records.
Key features
- User Validator Field - validates username and password of a system user
- Logged User Validator Field - validates a password of a currently logged in user
- Issue Signs Information - issue tab panel with the history of the signatures
- Search - you can filter tickets by users who signed.
Reviews for cloud
(21)Sign in to write a review
Hi. I am planning to support this but only for the newest JIRA versions for now.
Will do some tricky settings in the next release
Done
Reviews for server
(21)Sign in to write a review
Hi Quang Pham, Electronic Signature Fields app itself contains custom fields (Logged User Validator/ Non logged User Validator) for checking the user credentials. They enable you to verify the signature on your Issue screens. Regards, Cprime
Hi there,
Thank you for your feedback & excellent question. At this moment we are gathering interest as well as researching its feasibility in Jira cloud so that we can evaluate whether it would make sense to implement Electronic Signatures in Jira cloud.
Cheers,Cprime
Hi. I am planning to support this but only for the newest JIRA versions for now.
Will do some tricky settings in the next release
Reviews for Data Center
(21)Sign in to write a reviewHi. I am planning to support this but only for the newest JIRA versions for now.
Will do some tricky settings in the next release
Done
Cloud Pricing
Server Pricing
Data Center Pricing
| 10 users$10 | 25 users$90 | 50 users$180 | 100 users$270 | 250 users$360 | 500 & upAdditional pricing details |
| 50 users$400/year | 100 users$600/year | 250 users$800/year | 500 users$2,000/year | 750 users$3,000/year | 1000 & upAdditional pricing details |
Pricing FAQ
- How does server app pricing work?
Server products and apps are hosted on your servers. This app is sold as a perpetual license, and the purchase price includes 12 months of maintenance (support and version updates).
You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your Atlassian product and app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).
If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.
- How do I determine my server pricing?
Apps are billed based on the number of users in your Atlassian product. For Jira 7.0 or later, the app tier should match the maximum tier of the licensed Jira products on your instance. For example, if you're running Jira Software (500 users) and Jira Service Desk (25 agents) on the same instance, you should purchase the 500-user tier for apps. For versions of Jira prior to 7.0, the app tier should match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses should match exactly. Note: While this app has features specific to Jira Service Desk, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.
- Can I install this app in a Data Center product?
Yes, this app has a Data Center approved version. If you're using a Data Center product, you should install the Data Center version of the app.
- What type of license do I need if I'm using this app in a Data Center product?
Because this app has a Data Center approved version, you should purchase a Data Center license for the app.
If you already own a server license for this app, you can continue using the server license in your Data Center product for a limited period of time.
- Do you offer academic, community, or open-source licenses for server apps?
For server apps, academic licenses are available at a 50% discount if you have an academic license for your Atlassian product.
Community and open-source licenses are available for server apps. Learn more about community and open source licenses.
- Can I extend my free trial?
For server apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian product, and you're all set.
- How can I buy apps for my legacy Jira Server or Confluence Server license?
If you own a legacy Jira Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy app pricing is no longer available. You have two options for app purchasing:
- Purchase the app at the non-legacy Unlimited (10000+ users) tier.
- Renew your Jira or Confluence license at a non-legacy tier, then purchase the app at the same tier.
Pricing FAQ
- How does Data Center app pricing work?
Data Center apps are sold as an annual subscription. You are eligible for support and version updates as long as your subscription is active.
If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.
- How do I determine my Data Center pricing?
Apps are billed based on the number of users in your Atlassian product. For Jira 7.0 or later, the app tier should match the maximum tier of the licensed Jira products on your instance. For example, if you're running Jira Software (500 users) and Jira Service Desk (25 agents) on the same instance, you should purchase the 500-user tier for apps. For versions of Jira prior to 7.0, the app tier should match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses should match exactly. Note: While this app has features specific to Jira Service Desk, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.
- Can I install this app in a Data Center product?
Yes, this app has a Data Center approved version. If you're using a Data Center product, you should install the Data Center version of the app.
- What type of license do I need if I'm using this app in a Data Center product?
Because this app has a Data Center approved version, you should purchase a Data Center license for the app.
If you already own a server license for this app, you can continue using the server license in your Data Center product for a limited period of time.
- Do you offer academic, community, or open-source licenses for Data Center apps?
For Data Center apps, academic licenses are available at a 50% discount if you have an academic license for your Atlassian product.
Community and open-source licenses are not available for Data Center apps. Learn more about community and open source licenses.
- Can I extend my free trial?
For Data Center apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian product, and you're all set.
Cprime provides support for this app.
Cprime provides support for this app.
Vendor support resources
Find out how this app works.
Collaborative documentation platform hosted by this vendor.
Atlassian-hosted discussions connect you to other customers who use this app.
Vendor support resources
Find out how this app works.
Collaborative documentation platform hosted by this vendor.
Atlassian-hosted discussions connect you to other customers who use this app.
Versions
Version 3.0.1-jira8 • Jira Server 8.0.0 - 8.11.1 • Released 2020-07-17
Summary
New features
Details
In this version we've:
- eliminated extra steps on multiple users transition
- introduced email frequency setting
Versions
Version 3.0.1-jira8 • Jira Data Center 8.0.0 - 8.11.1 • Released 2020-07-17
Summary
New features
Details
In this version we've:
- eliminated extra steps on multiple users transition
- introduced email frequency setting
Installation
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new apps or Find new add-ons from the left-hand side of the page.
- Locate Electronic Signature Fields via search. The appropriate app version appears in the search results.
- Click Try free to begin a new trial or Buy now to purchase a license for Electronic Signature Fields. You're prompted to log into MyAtlassian. Electronic Signature Fields begins to download.
- Enter your information and click Generate license when redirected to MyAtlassian.
- Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Jira instance.
To find older Electronic Signature Fields versions compatible with your instance, you can look through our version history page.
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new apps or Find new add-ons from the left-hand side of the page.
- Locate Electronic Signature Fields via search. The appropriate app version appears in the search results.
- Click Try free to begin a new trial or Buy now to purchase a license for Electronic Signature Fields. You're prompted to log into MyAtlassian. Electronic Signature Fields begins to download.
- Enter your information and click Generate license when redirected to MyAtlassian.
- Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Jira instance.
To find older Electronic Signature Fields versions compatible with your instance, you can look through our version history page.
Similar apps
