---
title: "Route scan findings to GitHub Issues, Jira or Linear | Proofline Help"
description: "Create a ticket destination under Settings → Connections, then authorize the source repository if scan findings should produce tickets automatically. Check the tracker's write authorization before expecting tickets."
url: https://proofline.sh/help/route-scan-tickets/
---

[Help center](/help/)

# Route scan findings to GitHub Issues, Jira or Linear

Create a ticket destination under Settings → Connections, then authorize the source repository if scan findings should produce tickets automatically. Check the tracker's write authorization before expecting tickets.

## Configure a destination and authorize its repository

An organization administrator with a recent sign-in can configure destinations under **Settings → Connections → Ticket destinations**. Automatic tickets also need explicit authorization for each source repository by someone allowed to manage its settings.

1.  Select **Add destination**.
2.  Choose the tracker and target. For **GitHub Issues**, choose a **Repository**. Jira and Linear appear only when the connector is available for your organization; connect it first under **Connections → Integrations**.
3.  For Jira or Linear, choose an active **Connection** and its **Project** or **Team**. Enter the Jira transition ID in **Transition that closes a ticket**, or the Linear workflow state ID in **State a closed ticket moves to**.
4.  Enter a **Name** and describe **What belongs here**. Set **Labels**, **Owner team**, and **New tickets per day** as needed.
5.  Choose whether this is the **Default destination**, and leave **On** selected to accept new tickets.
6.  Select **Create destination**.
7.  Return to **Ticket destinations** and check its readiness. A tracker connection that only reads data needs write authorization before it can publish tickets.
8.  Under **Automatic tickets**, choose a **Repository** and select **Authorize repository**.

For an authorized repository, Proofline can open one ticket per reported scan finding that has an owner. A later scan or verified fix that resolves the finding closes its ticket. The default destination is used when no other destination fits.

Select a destination to edit its settings, then select **Save**. Clear **On** to stop new tickets there. **Delete** removes the destination and leaves tickets it already opened in place. Under **Automatic tickets**, **Stop** removes a repository's standing authorization.

## Related guides

-   [Schedule latent-risk scans](/help/latent-risk-scans/)
