💡 Still using the classic Drata experience? Refer to Workspaces - Ticketing Management for the original UI.
Use ticketing in Drata to create, triage, and track work for your compliance program from controls and tests, including tickets that are scoped to a specific workspace.
Workspace-aware ticketing lets you:
Create tickets from controls and tests in non-primary workspaces.
Route work to the right product or team by including the workspace name in the ticket data.
Allow workspace managers to manage tickets for only the workspaces they own.
Tickets created from a workspace still live in your external ticketing tool (for example, Jira or ServiceNow), but are linked back to the originating control or test in Drata.
Prerequisites
To create and manage tickets in the New Experience:
You must have one of these roles:
Admin
Information Security Lead
Workspace Manager (for the specific workspace)
You cannot be using the Risk Manager role to create workspace-level tickets.
You must have an active connection to a supported ticketing provider with Write Access enabled.
Risk Management is not supported for creating tickets per workspace. Ticket creation in the Risk Management area continues to work at the tenant level.
Jira Automation rules are not applied on a per-workspace basis; they continue to operate at the global (tenant) level.
If you do not see ticketing options where expected, confirm your role and ticketing connection with an Admin.
How ticketing works with workspaces
When you select a workspace, any tickets created from that context are associated with that workspace.
Key behavior:
When you create a ticket from a control or test in a non-primary workspace, Drata:
Associates the ticket with that specific workspace.
Sends the workspace name into the ticket payload (for example, in the ticket title or a custom field) so teams working in Jira, ServiceNow, or other tools can see where the ticket came from.
Workspace Managers can:
Create tickets from controls and tests in their assigned workspaces.
View and manage existing tickets for those workspaces from within Drata.
Create a ticket from a control (New Experience)
Select a workspace
Use the workspace selector in the app header to choose the workspace you want to work in (for example, a specific product or environment).
Open the control
Navigate to the Controls area for that workspace.
Search for and open the control that needs follow-up work.
Open the ticketing panel
Select the side arrow to create tickets
Review any existing tickets already linked to this control.
Create the ticket
Select Create ticket.
Choose the ticketing provider (if prompted) and fill in required fields such as:
Project or board
Issue type
Summary and description
Priority or assignee (if applicable)
Confirm that the workspace name appears in the auto-generated title or in the workspace field, so downstream users can see the origin.
Save and link
Select Create (or the equivalent action).
The new ticket appears in the control’s ticket list in Drata, linked to that control and workspace.
Create a ticket from a test (New Experience)
Select a workspace
From the workspace selector, choose the workspace whose tests you want to work on.
Open the test
Navigate to the Monitoring page within that workspace.
Open the specific test that requires investigation or remediation.
Create the ticket
In the test details view, go to the Tickets section or tab.
Select Create ticket and complete the required fields for your connected ticketing provider.
Confirm that the workspace name is included in the ticket information so the owning team can quickly identify scope.
Track ticket status
After creation, the ticket shows in the test’s ticket list, with status synchronized from your ticketing tool (where supported).
Limitations and tips
Workspace-level ticketing is currently available for controls and tests; Risk Management tickets remain global.
Jira-specific automation and configuration (such as JQL-based rules) still apply at the tenant level, not per workspace.
For the cleanest downstream workflows:
Use consistent naming conventions in ticket summaries.
Consider filters or boards in your ticketing tool keyed on the workspace name or related field, so individual product or team owners can quickly find their tickets.