💡 Still using the classic Drata experience? Refer to Jira Tickets as Evidence for the original UI.
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.