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.

BEFORE DIVING IN

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, you have the option to grant ‘Write Access’ to Drata. This allows you to create Jira tasks associated with a specific Control, Test, or Risk (in risk management) directly from Drata.

You can enable 'Write Access' during the initial setup or by editing the connection later. If you enable it after the connection is established, you do NOT need to reconnect Jira.

NOTE 1: You can connect multiple Jira accounts in Drata, and enable 'Write Access' for multiple of these connections.

NOTE 2: You must be logged into the Jira connection you are editing to be able to make changes.

NOTE 3: If you are unable to create a ticket or to enable/disable 'Write Access', you might not be logged into the corresponding Jira account.

NOTE 4: If you ever see any inconsistencies between your company’s Jira board and Drata, please refresh Drata to see the updated information.

Create Ticket Automation rules

Go to the Settings page. To go to the Settings page, select your username and then Settings.
On the Settings page, select Ticket Automation.
Choose a workspace, if you have multiple workspaces. If no workspace option appears, your primary workspace is the only available option for ticket automation.
Choose an event.
- Choose the event that will trigger the ticket automation. Once saved, this event cannot be changed.
- The events are: A control’s readiness is “Not Ready”, A test result is “Failed”, and A test result is “Error”.
Customize the scope. You can automate ticket creation based on a control event or test result.
- If you selected the A control's readiness is "Not Ready" event, you can specify even further based on the following configurations: Control monitoring, Evidence, Control owners, and Frameworks.
- NOTE: If you specify multiple control owners, they will be evaluated with AND logic, not OR. All specified control owners must be owners on the same control for that control to meet the rule's conditions. An alternative would be to build a rule for each control owner.
- If you selected the A test result is "Failed" or A test result is "Error" event, you can specify based on the categories and test type if applicable.
  - Categories, except Infrastructure, have ticket automation available only for Production tests. If you select a category, except for Infrastructure, the test type will default to production, and you won't have the option to choose a codebase test.
  - If you choose All categories (which includes the Infrastructure category) or specifically Infrastructure category, you can automate ticket creation based on where the test failed or encountered an error. The options are:
    Production tests only: These tests are run in a live, deployed environment.
    Codebase tests only: These tests are performed on development code before it is deployed.
    Both production and codebase tests: Automate ticket creation for both environments.
Select the ticket destination. After specifying the event and scope, select the Jira project and Ticket type.
Set up ticket details and enter the required fields for the Jira ticket type. Drata automatically sets the Jira Summary and Description field.
- Required fields are configurable within Jira by an administrator.
- Some uncommon field types, such as radio buttons are not supported. Remove unsupported fields or request support from Drata.
- If you connect Jira in multiple workspaces, you will be able to create ticket rules in each workspace, but the Ticket Automation will only execute with the data of the primary workspace.
Finalize the ticket rule and name the ticket rule for easy identification in the rules list.

Ticket automation rules run overnight and create tickets for all matching events where an automated ticket has not previously been created. Below are examples of the “Summary” and “Description” values Drata automatically populates for each ticket.

A test result is “Failed” event:

A control’s readiness is “Not Ready” event

Edit and Delete Ticket Automation Rules

You can edit and delete ticket automation rules from the ticket automation rule list. You’ll also be able to select which workspace the rule applies to, when editing.

NOTE: Once a rule is saved, the event type cannot be changed. If you wish to change the event type, delete that rule and create a new one.