Skip to main content

​
Creating Tickets

Every finding in Krait has a Create Ticket button. Clicking it opens the ticket creation dialog, pre-filled with context pulled directly from the finding so engineers have everything they need without any manual input.
1

Click Create Ticket

Open any finding and click the Create Ticket button.
ticket_create_button
If Linear is not configured yet, Krait will prompt you to complete the integration before proceeding.
2

Fill in the dialog

The Create Linear Ticket dialog opens with the finding details already populated.
ticket_create_dialog
The dialog contains the following fields:
  • Issue Title - auto-filled with the vulnerability name. You can edit it before submitting.
  • Project - select the Linear project this ticket should be created under.
  • Team - becomes available after selecting a project. Choose the team responsible for remediation.
  • Assignee - becomes available after selecting a project. Optionally assign the ticket to a specific team member.
Below the fields, a read-only Vulnerability Details panel shows the context behind the finding:
  • Resource - the repository or asset where the vulnerability was found
  • Type - the finding type, such as API or Dependency
  • Severity - the severity level of the finding
  • CWE - the weakness identifier and full description
The Description field is auto-generated and contains a full technical breakdown of the vulnerability, including how it can be exploited and recommended remediation steps. You can review and edit it before submitting.
3

Create the ticket

Click Create Linear Ticket. Krait sends the issue to your connected Linear workspace and links it back to the originating finding.
Once created, the ticket is visible on the individual finding page and in the Tickets dashboard. On the Tickets tab of each finding, Krait displays:
  • A direct link to the Linear ticket
  • The associated Linear issue key (e.g., KRA-123)
  • Ticket status and assignee
  • Any other synced metadata supported by Linear (project, priority, workflow state)
These fields sync from Linear so your team always sees real-time information inside Krait.

​
How This Helps Your Team

  • Faster handoff from security to engineering
  • Clear traceability from vulnerability to ticket to remediation
  • Reduced context switching across tools
  • Transparent ownership and accountability