Skip to main content

​
Creating Tickets

1

Open a Vulnerability and Start Ticket Creation

  • To create a Linear ticket:
    • Navigate to Vulnerabilities → Details for the issue you want to escalate.
    • Click the Create Ticket button in the top-right action bar.
    • This opens the Linear ticket creation dialog.
ticket_create_button
If Linear is not configured yet, Krait will prompt you to complete the integration before proceeding.
2

Ticket Creation Dialog

Selecting Create Ticket opens a structured dialog pre-filled with context extracted from the vulnerability. This ensures accuracy and drastically reduces manual effort.The dialog includes:
  • Issue Title
    Auto-generated using the vulnerability’s name. You may edit as needed.
  • Assignee
    Optional field allowing selection of a Linear workspace member responsible for remediation.
  • Vulnerability Details Panel (read-only)
    • Resource name
    • Severity
    • Category
    • CWE
    • File/API location
  • Description
    A comprehensive, auto-generated description that includes:
    • Summary of the vulnerability
    • Technical breakdown and potential impact
    • Recommended remediation guidance
ticket_create_dialog
This ensures the Linear issue contains all the information engineers need - without manual copy/paste.
3

Confirmation

After reviewing the fields, select Create Linear Ticket to submit.During this step:
  • Krait sends the issue to the connected Linear workspace
  • The ticket is created under the configured Team and Project
  • A confirmation message appears stating:
    Linear ticket created successfully.
The Linear issue is now linked to the vulnerability, allowing teams to move seamlessly from discovery to remediation.

​
After Ticket Creation

Once a Linear ticket is created, Krait automatically links it back to the originating vulnerability and updates the interface to reflect the new association.

​
Where You Can See the Ticket

The ticket now appears under the Tickets tab within the vulnerability details page.
vuln_preview
  • Each linked ticket displays:
    • Issue title (as created in Linear)
    • Project name
    • Assigned engineer
    • Current Linear status (e.g., Backlog, In Progress, Done)
    • Priority (when available)
These fields sync from Linear so your team always sees real-time information inside Krait.

​
Ticket Visibility Across Krait

The newly created Linear issue is also listed in the Tickets section of Krait’s main navigation, where you can filter and review all tickets across resources.

​
Linked Metadata Displayed on the Vulnerability

On the vulnerability details page, under the “Tickets” tab, Krait shows:
  • 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)

​
How This Helps Your Team

This unified view enables:
  • Faster handoff from security to engineering
  • Clear traceability from vulnerability → ticket → remediation
  • Reduced context switching across tools
  • Transparent ownership and accountability
Krait ensures every ticket remains fully synchronized with Linear so that your team can track remediation progress without leaving the platform.