Customers have installed this app in at least 69 active instances.
    by InLabsfor JIRA Server 7.0.0 - 7.4.3 and more versions
    Versions available for JIRA Server 6.0 - 6.4.14
    InLabs supports this app.

    Get support

    Meet CFR Part 11 in JIRA with Electronic Signature plugin

    Meet CFR Part 11 in JIRA with Electronic Signature plugin

    Easy to install

    Easy to use

    PDF Snapshot

    It's really simple. Just add a new customfield of type Electronic Signature. Add it to the proper screens and that all!

    To execute transition or edit users have to type valid credentials to go ahead. This will successfully prevent unauthorised actions on issues.

    Each successful authentication generates separate PDF snapshot. It contains issue's state during electronic signatures.

    More details

    Meet CFR Part 11 in JIRA with Electronic Signature plugin.

    How we can improve this plugin ? Please write at plugins@intenso.com.pl

    Follow us on Twitter @InTENSO10

    User reviews

    Sign in to write a review
    by Chen Hong on 2017-05-10
    Does it enforce E-sig during bulk change of multiple issues (e.g. Transition from Open to Closed Status)? Also how about updating issues status via JIRA REST APIs, can this E-sig be enforced?
    Was this review helpful?YesNo
    by Frank Trautwein on 2016-10-12
    Hello, the most recent version of your plug-in is four months old - which is ok if there weren't any significant security patches for Jira, which we installed a month ago (7.2.0) breaking compatibility. Ever-since we cannot use any of our workflows requiring electronic signatures as the plug-in is incompatible. Do you have any plans on fixing this anytime very soon? What is your policy about staying current with the Jira development and any possible bug fixes Atlassian provides? Thanks for your answer!
    3 out of 3 found this review helpful
    Was this review helpful?YesNo

    Hi, We have uploaded new version which is compatible with the latest JIRA version.


    Pricing details are loading…

    Paid-via-Atlassian pricing FAQ

    How does server app pricing work?

    Server products and apps are hosted on your servers. Licenses are perpetual and the purchase price include 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 host 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 host product. For JIRA Server 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 (50 users) and JIRA Service Desk (10 agents) on the same instance, you should purchase the 50-user tier for apps. For versions of JIRA Server 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.

    Do you offer academic, community, or open-source licenses?

    For server apps, purchase and renewal is half-price if you have an academic license for your Atlassian host product. Server apps are always free for community and open-source licenses.

    For more details about qualifying for special licenses, see here.

    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 host 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.

    Learn more

    InLabs provides support for this app.

    Vendor support resources


    Find out how this app works.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this app.


    Version 2.0.7 JIRA Server 7.0.0 - 7.4.3 Released 2017-07-31


    Bugfix release


    Electronic signature - snapshot distorted when priority is hidden - bug fix


    1. Log into your JIRA instance as an admin.
    2. Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
    3. Click Find new add-ons from the left-hand side of the page.
    4. Locate Electronic Signature via search. The appropriate app version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for Electronic Signature. You're prompted to log into MyAtlassian. Electronic Signature begins to download.
    6. Enter your information and click Generate license when redirected to MyAtlassian.
    7. 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 versions compatible with your instance, you can look through our version history page.

    Similar apps