Skip to main content

Hai Linear Integration

Organizations: Automatically turn HackerOne reports into organized, deduplicated Linear issues

Need to create issues manually? The manual Linear integration handles issue creation with bidirectional sync. The integration below is for automated creation and deduplication via configurable triggers.

You can integrate with Linear to sync information between your HackerOne report and your Linear issue.

Step 1: Connect Linear Workspace

  1. Navigate to Organization Settings → Integrations → Linear → New Linear Workspace.

  2. Click the Set up new integration button.

  3. Configure your Linear workspace connection with HackerOne

    1. Workspace Name: Provide a descriptive name for your workspace (e.g., "Linear prod")

    2. Workspace Description: Optional description to help identify the workspace

    3. Linear API Token: Generate and paste your Linear API token

      1. Go to Linear → Settings → API

      2. Create a new API token with appropriate permissions

      3. Copy and paste the token into the field

  4. Once connected, you'll see: "Connected to Linear workspace: user"

    Screenshot 1: Connect Linear

Step 2: Map Programs to Linear Teams

Use the dropdown to assign Linear teams to your HackerOne engagements.

  • Select a Linear team for each HackerOne program.

  • Use the dropdown to assign teams (for example, “Security team”).

  • You can map multiple programs to the same Linear team.

Note: If you leave a program unmapped, the system suggests a team when creating issues based on report context.

Step 3: Configure Automation Setup

Define when Linear issues should be automatically created.

  1. Enable or disable Automatic issue creation.

  2. Select a trigger for when issues should be created:

    • When a report moves to pending program review (PPR)

    • When a report is triaged

    • When a report is assigned

    • Custom report state transitions

When enabled, the system automatically creates a Linear issue when the selected trigger fires. It does not create duplicate issues if a similar issue already exists.

Note: The trigger must fire for automation to work. For example, if you select PPR, issues are only created when reports reach that state.

Step 4: Configure De-Duplication Control

Configure how the Linear Agent handles duplicate findings

Confidence Threshold

Set the Confidence threshold for duplicate detection. Choose a value between 0% and 100% (default is 80%). Lower thresholds result in more aggressive de-duplication.

  • Default: 80% (Recommended)

  • Range: 0% - 100%

  • Impact: Lower thresholds = more aggressive de-duplication

Tuning the Threshold:

  • 80-100%: Conservative - only links to very similar issues

  • 60-80%: Balanced - recommended for most teams

  • Below 60%: Aggressive - may link to less similar issues

How De-Duplication Works

The Linear Agent performs a mandatory duplicate check before creating any issue:

  1. Search by title keywords: Uses key words from the report title to find similar issues

  2. Search by asset: Combines asset name with vulnerability type (e.g., "api.example.com XSS")

  3. Review all search results: Checks if any issue describes the same vulnerability on the same asset

  4. Compare technical details: Analyzes issue titles and descriptions for technical similarity

  5. Link or create: If a duplicate is found (above confidence threshold), links to the existing issue; otherwise, creates a new issue

Setup Complete

After completing all 4 steps above, click Update to save your configuration. Your Linear workspace will appear in the Integrations page under Hai integrations. Click View to manage or edit the configuration at any time.

Did this answer your question?