💡 Still using the classic Drata experience? Refer to Ticket Automation (Jira-only) or Create or Link Jira Tickets in Drata for the original UI.
Managing your security compliance can require coordination and collaboration with other members of your organization. Drata makes this easier by integrating with the tools you already use on a daily basis, including Jira. By configuring ticket automation rules in Drata, you can have tickets automatically opened for key control and test events.
Prerequisites
Users with Admin access and DevOps Engineer can create ticket automation rules within Drata; however, a user must have Admin access to set up or edit the Jira connection.
'Write Access' can be enabled when creating the initial Jira connection or turned on after the connection has been made (by editing the connection).
Drata pulls in the required Jira fields as determined by your specific Jira configuration, including Projects, Task Types, and other fields.
Enable write access for Jira connection
When Jira is connected to Drata, you can optionally enable Write Access. Write Access allows Drata to create Jira tickets directly from:
Controls
Monitoring tests
Risk Management
You can enable Write Access:
During the initial Jira connection setup, or
Later by editing the existing connection
If you enable Write Access after the connection is already established, you do not need to reconnect Jira.
Important Notes
You can connect multiple Jira accounts in Drata and enable Write Access for more than one connection.
To make changes, you must be logged into the specific Jira account you are editing.
If you cannot create tickets, verify you are logged into the correct Jira account.
If Jira and Drata appear out of sync, refresh Drata to load the most up-to-date information.
Create a Ticket Automation Rule
Follow these steps to automatically create Jira tickets based on control or test events.
Step 1: Open Ticket Automation
Go to Settings
Select Ticket automation
If you have multiple workspaces, choose the workspace for the rule If no workspace selector appears, the rule applies to your primary workspace
Step 2: Choose a Trigger Event
Select the event that will create a Jira ticket.
Available trigger events:
A control’s readiness is Not Ready
A test result is Failed
A test result is Error
Important: Once the rule is saved, the trigger event cannot be changed.
To change the event type, you must delete the rule and create a new one.
If the Trigger Is: Control Readiness = “Not Ready”
You can narrow the scope using:
Control monitoring status
Evidence requirements
Control owners
Frameworks
If multiple control owners are selected, Drata evaluates them using OR logic (Any control assigned to at least one selected owner will match the rule).
If the Trigger Is: Test Result = “Failed” or “Error”
You can filter by:
Test category
Test type (when available)
Test Type Behavior
Most categories only support automation for Production tests
Infrastructure supports additional options
If you select:
A category other than Infrastructure → Production tests only
Infrastructure or All categories → you can choose:
Production tests only (live environment)
Codebase tests only (pre-deployment testing)
Both production and codebase tests
Step 3: Customize the Rule Scope
When creating a ticket automation rule for test results (Failed or Error), you must choose which test categories to include.
Selecting All includes Infrastructure tests. Because Infrastructure tests can run in different environments, Drata will prompt you to choose which test types to automate:
Production tests only
Tests run in a live, deployed environment.Codebase tests only
Tests run against source code before deployment.Both production and codebase tests
Tickets will be created for failures in either environment.
If you choose one or more specific categories (excluding Infrastructure):
Ticket automation applies only to Production tests
Codebase test options are not available
To configure this:
Select Specific categories
Choose one or more categories
Select Continue
Step 4: Select the Ticket Destination
Choose and complete the required Jira fields.
How Automation Runs
Ticket automation rules:
Run overnight
Create tickets for all matching events
Do not create duplicate automated tickets for the same event
If Jira is connected in multiple workspaces:
You can create rules in each workspace
Automation execution runs using data from the primary workspace