Use Electronic Signatures Compliant with Title 21 CFR Part 11

Establish compliance across your Jira within 5 minutes with our app Electronic Signatures. Watch our quick demo video or read the transcription below to get started.




Video Transcription

Hello, and welcome to today’s webinar on how to establish compliance across your Jira within five minutes, using seen our app Electronic Signatures. I’m your host today, Chelsea Bauer. I’m the product marketing manager here at Anova Apps and I have over six years of experience in product marketing. I’m passionate about promoting products that resolve user problems, that are easy to use, and boost efficacy among teams.

We’ll be focusing on some of the issues that come with digital security compliance, and I’ll walk you through how Electronic Signatures can resolve those governance issues in just a few steps. Let’s get started.

The problem. Compliance is an issue for customers in regulated industries that must abide to the government’s processes in order to stay compliant with the FDA’s 21 CFR Part 11.

When these companies get audited, they’re required to show proof of compliance, so whether if it’s a paper trail or digital trail, we’ve seen many teams struggle to keep all the necessary details on tickets up to date. Such as who all needs to sign off on this item? Did we get this person’s signature? Was it signed and recorded, and so on? And that alone can be daunting when governance is lacking.

While any audit can be nerve-wracking, the solution to your compliance needs is quite simple. Spoiler alert, it’s Electronic Signatures for Jira.

It’s the perfect way to increase data security and ensures compliance because it sets user credentials according to the technical elements of 21 CFR Part 11, which defines the criteria under electronic records and signatures to be trustworthy, reliable, and equivalent to paper records.

The key benefits include it’s available across all the hosting options in Atlassian, so Cloud, Data Center and Server. It locks out any unauthorized actions and Jira issues. Unique pins are individually assigned to each user, so making traceability a breeze and all your records are compliant.

Let me show you how it works. Here I made a sample ticket in my Cloud instance. You have two options for launching Electronic Signatures, you can go here on the icon, or if you prefer, you can go to the actions drop-down menu here and click on E-Signatures. Regardless of which option you decide to use, this screen will pop up and you can see the fields here, name, time, date, and the signature pin.

But if this is your first time using it, you will need to get your pin assigned. To make that happen, you just click send pin and it’ll go straight to your email and this confirmation window will pop up.

Head over to your email, search for the subject line your e-signatures pin, and on the first line, you’ll see that four-digit code.

You’re going to copy it and then take it back here to the dialogue window and into the four code right here and click sign.

After that, you can refresh the page and you’ll see the activity is updated in the comment section below. The app supports users across multiple time zones so that timestamp down below will reflect according to that user’s time zone.

One last note, if there’s any reason you need to print these out or need to share them externally in a different format, you can go to our actions drop-down menu right here and click on export Word.

Then you’ll get this download of the report in Word and it’ll show you all these populated fields with a little more info. You can print these and store them however you need for your record keeping.

That is it, so you can download a free trial and test it out yourself. If you have any questions, please email us at and we’ll see you next time.