> ## Documentation Index
> Fetch the complete documentation index at: https://docs.krait.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating Tickets

> With just one click, teams can transform security findings into engineering problems thanks to Krait's seamless integration with Linear. With support for both global and per-resource setup, this integration guarantees that vulnerability data is converted into tasks that can be implemented inside your current linear processes.

## 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.

<Steps>
  <Step title="Click Create Ticket">
    Open any finding and click the **Create Ticket** button.

    <Frame>
      <img src="https://mintcdn.com/krait/9ioPUQVgYHbGs9dJ/tickets/images/ticket_create_button.png?fit=max&auto=format&n=9ioPUQVgYHbGs9dJ&q=85&s=85decb96e4272fc122941f8a1c320d33" alt="ticket_create_button" width="2226" height="140" data-path="tickets/images/ticket_create_button.png" />
    </Frame>

    <Info>
      If Linear is not configured yet, Krait will prompt you to complete the integration before proceeding.
    </Info>
  </Step>

  <Step title="Fill in the dialog">
    The **Create Linear Ticket** dialog opens with the finding details already populated.

    <Frame>
      <img src="https://mintcdn.com/krait/9ioPUQVgYHbGs9dJ/tickets/images/ticket_create_dialog.png?fit=max&auto=format&n=9ioPUQVgYHbGs9dJ&q=85&s=bba08343ac15bf9b70d5e676667b3824" alt="ticket_create_dialog" className="mx-auto" style={{ width:"72%" }} width="1382" height="1720" data-path="tickets/images/ticket_create_dialog.png" />
    </Frame>

    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.
  </Step>

  <Step title="Create the ticket">
    Click **Create Linear Ticket**. Krait sends the issue to your connected Linear workspace and links it back to the originating finding.
  </Step>
</Steps>

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