Connecting Linear to Drata allows for automated checks and evidence collection to prove to auditors that your company follows its vulnerability management policy and procedures.
Prerequisites
Make sure you have admin access to your company's Linear account.
Connect Linear to Drata
Select 'Connections' from the side navigation menu.
Search for 'Linear' to select the connect button for the Linear integration.
Complete the required fields in the slide-out panel.
If you do not use 'Security' as the label within Linear to categorize tickets as security issues, be sure to update the 'Security Label' within the panel.
To create Linear tickets from Drata, enable Write Access.
After selecting 'Connect your Linear account,' you'll be redirected to Linear. Choose the workspace you wish to sync with Drata. Once you've chosen the workspace, you'll return to Drata. For further steps, refer to the sections below.
Create Linear tickets through Drata
Note: To create tickets, ensure that within the Linear connection that Write Access is enabled.
The places you can create tickets are: Control Details, Test Details, or Risk Details (in Risk Management) drawer. If there are no tickets or tasks currently associated to a Control, Test, or Risk, you will be prompted to create one to get started. Select Create ticket to start the process.
Now, you will enter the ticket configurations and details. A multi-step modal will appear. Depending on your Linear configurations the following sections may differ.
Destination
If you use multiple ticketing systems, you will have to select Linear for the destination.
Team
Select the Linear team or workspace you would like to sync.
Ticket details
Lastly, enter the ticket details. The title and description will be auto-populated, but you can always edit the title and description if you'd like. You can also optionally add an assignee and a Parent Issue. The Parent Issue field allows you to search for and select an existing issue. If a parent issue is added, the ticket will be created as a sub-issue under the selected parent.
We’ve introduced 7 new fields that customers can leverage when creating Linear issues from Drata. All of the new fields are optional. Those fields are: Status, Priority, Project, Estimate, Labels, Cycle and Due Date. We need to update the “Ticket Details” section to include these new fields that we support.
Status – Single Option Dropdown
Indicates the current progress of the issue
Priority -> Single Option Dropdown
Associates the importance of the issue
Project -> Single Option Dropdown
Associates the issue with a specific project
Cycle -> Single Option Dropdown
Links the issue to a time-boxed period, such as a sprint. Cycles can fall into one of three time periods: Previous, Current, or Future .
Current and Future Cycles: When an issue is added to a Current or Future cycle, its status will be updated to a status type equal to "Ready."
Previous Cycles: When an issue is added to a Previous cycle, its status will be updated to a status type equal to "Completed."
Note: If the selected cycle and status are not aligned, the system will automatically overwrite the status to match the requirements of the chosen cycle when the issue is created.
Estimate - Single Option Dropdown
Indicates the estimated complexity or size of the issue (e.g., points or t-shirt sizes). The estimated values are determined by the settings the user sets in Linear. Estimates can be customized in Team Settings > General > Estimates, where admins can enable zero values, extended point systems, count un-estimated issues or disable the field entirely.’
Labels -> Multiple Option dropdown
Categorizes the issue using predefined labels
Due Date - Date
Indicates when the issue is expected to be completed
Once you get to the ticket details page, fill out the fields to create your issue. The Title is the only required field—the rest are optional and can be added or not based on your needs
Title (Required) – The name of the issue. Auto-populated but can be edited.
Description (Optional) – Details about the issue. Auto-populated but can be edited.
Assignee (Optional) – Assigns the issue to a specific user.
Parent Issue (Optional) – Links the issue under an existing issue.
Status (Optional) – Tracks the issue’s progress.
Priority (Optional) – Defines the issue’s importance.
Project (Optional) – Associates the issue with a specific project.
Cycle (Optional) – Links the issue to a sprint or time-boxed period.
Issues in a Current or Future cycle will have their status set to Ready.
Issues in a Previous cycle will have their status set to Completed.
If the selected cycle and status don’t align, the system will automatically adjust the status.
Estimate (Optional) – Represents the complexity or size of the issue, values provided are based on team settings.
Labels (Optional) – Categorizes the issue using predefined tags.
Due Date (Optional) – Specifies when the issue should be completed by.
Once all necessary fields are filled out, you can proceed with creating the issue.