⚠️ Select your experience
The steps depend on your interface version. Select a link to skip to the instructions for your version.
Customers who joined Drata on or after Feb 24, 2026 are automatically on the New Experience.
Instructions for the New Experience ⬇️
Overview
Many compliance and security activities are managed in Jira. Drata allows you to link closed Jira tickets as evidence in the Evidence Library so auditors can review proof of work without leaving Drata.
Jira tickets help demonstrate remediation, investigation, or approval activities tied to controls.
Prerequisites
Make sure the following requirements are met:
Drata roles: You must have one of these roles.
Admin
Information Security Lead
Workspace Manager
Control Manager
Jira connection: Jira must be connected to Drata. Refer to Connecting Jira to Drata for setup instructions.
Ticket requirements:
The Jira ticket must be closed before it can be added as evidence.
Any attachments on the ticket must be under 25 MB.
Add a Jira ticket as evidence
Go to Compliance > Evidence.
Select Create Evidence.
Enter a name and description for the evidence.
For Source, select Ticketing provider.
Enter the Jira ticket URL using this format:
https://your-domain.atlassian.net/browse/PROJ-123.The Jira ticket must belong to a Jira account that's already connected to Drata.
Enter a creation date and renewal date.
Renewal dates determine whether the linked control remains ready.
Enter the owner.
(Optional) Link the evidence to one or more controls by selecting Link control.
Select Save.
The Jira ticket is added to the Evidence Library and can now contribute to control readiness.
View or update Jira ticket evidence
Go to Compliance > Evidence.
Use filters to narrow the Source to Ticket.
Select the evidence item to open its details.
In the Current artifact section, you can:
Update creation or renewal dates
Open the Jira ticket
Download a ZIP file containing the ticket PDF and attachments
Previous versions appear in the Past artifacts tab.
Instructions for the Classic Experience ⬇️
Many compliance and security tasks are coordinated through Jira. With Drata, you can link compliance evidence that exists in Jira through our Evidence Library.
Before Diving In…
Admins, Information Security Leads, Workspace Managers, Control Managers can add new evidence to the Evidence Library.
You will need to make a Jira connection in order to use this feature. Go to Connecting Jira to Drata to learn how to connect Jira or Creating Jira Tickets via Drata to learn how to create tickets in Drata.
Attachments to tickets that are linked must be under 25 MB.
Tickets must be closed in order to be added as evidence.
Here's How
Add a Jira Ticket as Evidence
On the left navigation menu, select Evidence Library under the compliance section. On the Evidence Library page, select "Add Evidence".
Enter a name and description on the 'Add Evidence' drawer. You are the default owner of the evidence. To change the owner, delete yourself by selecting the X icon and enter the owner of the evidence.
Select "Ticketing provider" as your source.
After selecting the source, a confirmation message is shown that you are connected to Jira.
Enter the ticket URL with the following format: https://examplejira.atlassian.net/browse/PROJ-123.
Note: You can only enter the ticket URL after selecting a 'Ticketing provider' as the source.
The Jira domain in the URL should match your Jira connection(s).
Enter a creation date and a renewal date. Go to Evidence Renewal Date for more information about renewal date.
Link controls to your evidence by selecting 'Link control' in the linked controls section.
Save to add your evidence to the Evidence Library.
View Jira ticket evidence
On the Evidence library page, search and select the evidence. In the evidence drawer, the evidence is shown under the source section. Select View to view the ticket in Jira. Select Download to download a zipped folder with the PDF file of the ticket and its attachments. Select Update to edit the Jira link, creation date, and renewal date. The update does not synchronize any changes made in Jira to that ticket.