99
Customers have installed this app in at least 99 active instances.
    by InLabsfor Jira Server 7.1.0 - 8.2.2 and more versions
    Versions available for Jira Server 6.0 - 7.0.11
    Unsupported
    Jira Service Desk
    This app is compatible with Jira Service Desk.
    Supported
    InLabs supports this app.

    Get support

    Jira Service Desk
    This app is compatible with Jira Service Desk.
    Unsupported
    Jira Service Desk
    This app is compatible with Jira Service Desk.

    Meet CFR Part 11 with electronic signatures on Jira issues

    Meet CFR Part 11 with electronic signatures on Jira issues

    Meet CFR Part 11 with electronic signatures on Jira issues

    Quick and easy setup

    Secure users' actions on Jira issues

    Track and export authentication attempts

    Add a dedicated custom field to Jira. Add it to the proper screens. Configure the options. Done!

    Make users provide credentials to execute transitions. Prevent unauthorised actions on Jira issues. Get your Jira compliant with the FDA regulation CFR 21 part 11.

    Generate PDF snapshots of successful authentications. Add them as attachments and provide external comments to display on the Customer Portal. Save or print these files for audit purposes.

    More details

    This app makes users provide their credentials to execute transitions on Jira issues, which enables compliance with the FDA regulation CFR 21 part 11.

    The key features are:

    • Electronic Signature custom field
    • PDF snapshots of successful authentications with automatic adding to Attachments
    • Locking signatures after a number of failed login attempts

    Reach out to us at support@deviniti.com in case of any questions, or ask them on the Atlassian Community.

    Follow us on LinkedIn, Twitter and Facebook to track the latest news from our company and Atlassian ecosystem.

    Reviews for cloud

    (3)
    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
    InLabs

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

    Reviews for server

    (3)
    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
    InLabs

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

    Reviews for Data Center

    (3)
    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
    InLabs

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

    Cloud Pricing

    Server Pricing

    Data Center Pricing

    10 users$1025 users$10050 users$200100 users$300250 users$400500 & 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?

    This app does not have a Data Center approved version. Only apps meeting a set of performance requirements for large, clustered environments are approved for Data Center.

    However, while server apps are built for single-server deployments, many customers successfully install them in Data Center products. If you're using a Data Center product, Atlassian recommends you contact the vendor to determine compatibility at scale.

    Learn more about Data Center approved apps

    What type of license do I need if I'm using this app in a Data Center product?

    Because this app does not have a Data Center approved version, you should purchase a Server license if you decide to install this app in a Data Center product.

    Learn more about Data Center licensing

    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.

    Learn more

    InLabs provides support for this app.

    Vendor support resources

    Documentation

    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.

    Versions

    Version 3.1.0 Jira Server 7.1.0 - 8.2.2 Released 2019-02-15

    Summary

    Improvement & Bugfix release

    Details

    Compatibility with Jira 8.0 has been added. Problem with velocity has been fixed.

    Installation

    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 apps or Find new add-ons from the left-hand side of the page.
    4. Locate Electronic Signature for Jira 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 for Jira. You're prompted to log into MyAtlassian. Electronic Signature for Jira 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 for Jira versions compatible with your instance, you can look through our version history page.

    Similar apps