Update ticketing integration settings
Updates ticketing settings for the Linear or Jira integration. Set issue_label_enabled and issue_label_name to add a label to each issue that Strix creates. Personal tokens must belong to an organization administrator (parity with the dashboard).
Authorizations
API token obtained from the Tokens endpoint or CLI device login. Include as Authorization: Bearer <token>. Requests made with a managed CLI session also include X-Strix-Workspace: <organization_id> to pin a process to the workspace it started in; recovery endpoints report the current workspace after a concurrent switch.
Path Parameters
Ticketing integration provider.
linear, jira Body
Updates for a Linear or Jira integration.
Enable automatic issue creation for new findings.
Add the configured label to each issue that Strix creates.
Label name to add to each issue that Strix creates.
1 - 80Minimum severity that triggers automatic issue creation.
critical, high, medium, low Default Jira project or Linear team identifier.
Default Jira project or Linear team name.
Default Jira issue type.
Jira required field values for the default project.
Destination for each routed repository. Applies to Linear and Jira. This array replaces the stored repository routes: a repository that is not in the array loses its route. Send collection_id (the older project_id name is still accepted). For Jira, ticket_type and jira_field_values are optional and Strix rejects a route that misses a required field. Administrators only.
- Option 1
- Option 2
The destination for each finding source, keyed by scan (pentests), pr_review, and supply_chain. Applies to Linear and Jira. This object replaces the stored routes. To use the default destination for a source, set the key to null or leave the key out. Resolution order on a push: explicit destination on the push request, then repository route, then source route, then the default destination.
Provider user ID for the default assignee (see GET /integrations/{provider}/users). Strix checks the user with the provider. Set null to clear.
Ticket title template. Unknown placeholders are rejected. Set null to use {{title}}.
500Ticket description template. Unknown placeholders are rejected. Set null to use {{details}}.
20000Create one Linear project or Jira Epic per pentest and file its tickets under it.
Jira only. Maps severities (critical, high, medium, low) to { id } (the Jira priority ID, from GET /integrations/{provider}/priorities) or null. Send null to disable. Rejected for Linear. Administrators only.
Maps severities to a whole number of days (1-365) after creation for the due date, or null per severity. Send null to disable. Applies to Linear and Jira; new tickets only. Administrators only.
Response
Updated ticketing integration settings.
Ticketing settings for a Linear or Jira integration.
linear, jira critical, high, medium, low The destination for each finding source, keyed by scan (pentests), pr_review, and supply_chain. Applies to Linear and Jira. If a key is missing, Strix uses the default destination for that source. A repository route has priority over a source route.
Provider user ID that new tickets are assigned to. Linear: user ID. Jira Cloud: accountId. Jira Server: username. null leaves tickets unassigned.
Display name of the default assignee.
Template for the ticket title. Placeholders use {{name}}: title, severity, cve, cvss, target, endpoint, repository, pentest, source, strix_url, details. null means {{title}}.
Template for the ticket description. Same placeholders as title_template. null means {{details}}.
When true, Strix creates one grouping object per pentest and files its tickets under it: a Linear project in the destination team, or a Jira Epic in the destination project.
Jira only: maps each severity (critical, high, medium, low) to a Jira priority { id, name } or null (Jira's default). null disables the mapping; Linear priority always follows severity.
Maps each severity to a whole number of days (1-365) after ticket creation for the due date, or null (no due date). null disables. Applies to Linear and Jira; a snooze date always wins.
Connected repositories that a repository route can target. Present for administrators and service tokens.
Ticket destination for each routed repository. Present for administrators and service tokens.