Skip to main content

Documentation Index

Fetch the complete documentation index at: https://zeropath.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

ZeroPath integrates with Linear to push security findings as Linear issues. When a Linear issue is completed, the corresponding ZeroPath finding is automatically marked as resolved.

​
Setup

  1. Navigate to Settings → Integrations in the ZeroPath dashboard.
  2. Click “Connect Linear”.
  3. Authorize ZeroPath in the Linear consent screen.
  4. ZeroPath detects your Linear workspace and available teams.
The integration registers webhooks for all your Linear teams to enable bidirectional sync. Webhooks are configured with Issue and Comment resource types — Issue is required for status sync, while Comment is optional but enables smarter triage when tickets are closed. For manual webhook setup, select at minimum the Issue resource type. Adding Comment is recommended — it allows ZeroPath to analyze ticket comments and classify closed tickets more accurately.
Linear can be connected at either the organization level (shared across all members) or the user level (personal). Organization-level connections are recommended so that all team members can export findings to Linear without each needing their own connection. If both exist, the organization-level integration takes priority.

​
Manual Issue Export

From any finding in the ZeroPath dashboard:
  1. Click “Export to Linear” on the issue detail view.
  2. Select a Linear team and optionally an assignee.
  3. If you have a template configured (see Custom Templates), you can toggle “Use Linear Template” to apply it. Disable the toggle to manually edit the title and description before exporting.
  4. ZeroPath creates the Linear issue with vulnerability details.
The Linear issue ID is linked to the ZeroPath finding for tracking.

​
Bulk Export

You can export multiple findings to Linear at once:
  1. Select the findings you want to export from the issues list.
  2. Choose “Export to Linear” from the bulk actions menu.
  3. Select a Linear team and optionally an assignee.
  4. If a template is configured, you can toggle it on to apply the template to all exported issues.
  5. ZeroPath creates Linear issues for all selected findings in batches.
Findings that have already been exported to Linear are automatically skipped. After the export completes, you will see a summary showing how many issues were exported, skipped, or failed.

​
Automatic Ticketing

Configure automatic issue creation:
  1. Go to Settings → Integrations, select Linear from the sidebar, and open Auto-Ticketing.
  2. Set a score threshold — only findings above this score create Linear issues.
  3. Choose which scan types trigger issues.
  4. Select the Linear team to create issues in.

​
Auto-Assignment

Auto-ticketing supports automatic assignment of newly created Linear issues. You can configure assignment behavior in three ways:
  • Automatic (git blame) — ZeroPath analyzes git blame data for the affected file and matches contributors to Linear users by email or name. The best-matching Linear user is assigned to the issue. This is the default.
  • Fixed assignee — Always assign auto-created issues to a specific Linear user that you select.
  • Disabled — Do not assign auto-created issues to anyone.
When exporting issues manually (single or bulk), you can still pick an assignee in the export dialog. If you select an assignee manually, it always takes priority over the auto-assignment configuration.

​
Custom Templates

Auto-ticketing supports customizable title and description templates with variables:
  • {{severity}}, {{issueTitle}}, {{repositoryName}}, {{affectedFile}}, {{vulnClass}}, and more.
  • You can assign Linear labels (pulled from the selected team) and set a priority level (Urgent, High, Medium, Low, No Priority) for automatically created issues.
  • Custom variables can be mapped to ZeroPath finding data or set to static values.
To configure a template, open the auto-ticketing settings for Linear and click “Ticket Template”. The template editor provides:
  • Title and Description tabs for editing each template independently.
  • A variable picker to insert predefined or custom variables.
  • A live preview that shows how the template will render with example data.
  • The ability to reset to defaults at any time.
When exporting issues manually (single or bulk), you can choose whether to apply the configured template or use the default format.

​
Bidirectional Sync

When a Linear issue’s state changes to completed, ZeroPath automatically:
  • Analyzes ticket comments to determine the appropriate status — Resolved, False Positive, or Accepted Risk
  • If no comments are present or the Comment resource type is not enabled, the finding defaults to Resolved
  • If comments are present but the intent cannot be determined with confidence, the status change is skipped rather than defaulting to Resolved, preventing incorrect triage
  • Records the change in the finding’s audit trail
When you change the status of multiple findings at once (for example, marking many issues as false positive), ZeroPath syncs each update to Linear with controlled concurrency to stay within Linear’s rate limits. If an individual ticket update fails, the remaining updates continue — partial failures are logged without blocking the bulk action. This sync is powered by webhooks registered in Linear during setup. Unlike Jira, Linear webhooks do not expire. When you disconnect a Linear integration, ZeroPath automatically cleans up the associated webhooks. If multiple integrations share the same Linear workspace, webhooks are transferred to a remaining active integration rather than being deleted.

​
Troubleshooting

“Linear integration not found”
  • Ensure the integration is connected in Settings → Integrations.
Issues not syncing back
  • Verify the Linear issue was created through ZeroPath (only linked issues sync).
  • Check that the issue state changed to “completed” (other states are ignored).