Skip to main content
All CollectionsConnectionsGeneral Information
Creating Jira Tickets via Drata
Creating Jira Tickets via Drata

Create and view Jira tickets for Controls, Tests and Risk Management directly through Drata

Updated over a month ago

Once you integrate Jira to Drata, you can create tickets in Drata. Creating Jira tickets directly in Drata can help with managing your security compliance which require high coordination and collaboration throughout your organization.

Learn how to create and view yourJira tickets in Drata related to controls (DCF or custom), tests, and risks that are in Risk Management. You cannot create Jira tickets for risks in Risk Assessment.

BEFORE DIVING IN

  • Integrate Jira to Drata with write access enabled. Go to Connecting Jira to Drata for more information.

  • Ensure you have an admin or information security lead role to create Jira tickets in Drata.

Create Jira Tickets through Drata

Note: Ensure that you are in the desired workspace that has a Jira connection with write access. You can go to the Connections page and view your active Jira connections to view which workspaces are connected to Jira and if it is write-access enabled.

You can create Jira tickets within the drawers of controls, tests, or risks in Drata.

  1. Go to the Controls page and select a control or

  2. Go to the Monitoring page and select a test or

  3. Go to the Risk Management page and select a risk.

    • Note: Risk Management is part of the Advanced package and is separate from Risk Assessment. Learn more at https://drata.com/plans. Please contact your CSM or Support if you're interested in learning more and adding Risk Management to your account.

Within the drawer, scroll down to Ticket Management and select the Create ticket button.

Choose the destination

If you have multiple Jira connections, you must select the Jira connection you would like to write the Jira ticket to. Each Jira connection has an unique account alias to differentiate itself from other Jira connections. Select the alias to start the process of creating a Jira ticket in the desired Jira project.

Drata pulls in the available projects, tasks, and required fields specified in your company's Jira connection.

Choose a project

Select a Jira project.

Select a task type

Choose the type of ticket you'd like to create.

Note: The integration currently does not support subtasks. If subtasks is available, select another task type.

Fill in additional fields

Enter the required fields. The required fields are the ones specified in your Jira configuration. You can change what fields are required through your Jira settings.

  • Note: The entered description for the summary is displayed when you view your ticket in Drata.

Lastly, select the create button to create the ticket.

View and manage your Jira tickets

Note: Only tickets created in Drata for that specific control, test, or risk (in Risk Management) are displayed in Drata. Tickets created directly in Jira are not displayed.

You can view your Jira tickets within the drawers of controls, tests, or risks in Drata.

  1. Go to the Controls page and select a control or

  2. Go to the Monitoring page and select a test or

  3. Go to the Risk Management page and select a risk.

    • Risk Management is part of the Advanced package and is separate from Risk Assessment. Learn more at https://drata.com/plans. Please contact your CSM or Support if you're interested in learning more and adding Risk Management to your account.

The most recently created ticket is displayed at the top of the list. Each ticket displays the following information: summary of the ticket, the alias, and the Jira issue key.

Select the Jira ticket to view more information, download a pdf file about the ticket, remove the ticket from the Drata, or redirect to Jira for more information about the ticket by selecting the Manage ticket button.

To view the rest of the tickets, select View all tickets.

The tickets are divided into categories.

  • In Progress: Tasks in any open state as defined in your Jira instance such as Ready for Development or In Progress.

  • Closed: Tasks in any completed state as defined in your Jira instance such as Closed or Done.

Did this answer your question?