Linear Integration

Overview

The Linear integration connects your Fencer organization to a Linear workspace, allowing you to create and track Linear issues directly from vulnerabilities, vulnerability groups, detections, and secrets. When issue statuses change in Linear, Fencer automatically updates the corresponding items via bidirectional webhook sync.

Prerequisites

An active Fencer subscription.
The Administrator role in your Fencer organization.
A Linear workspace with permission to install OAuth applications.

How it works

Fencer connects to Linear using OAuth 2.0 with read and write scopes. Once connected, you can create Linear issues from individual vulnerabilities, detections, or secrets, or perform bulk operations across multiple items. Each created issue includes a rich description with relevant context such as severity, asset details, security standards, and remediation guidance. Fencer also attaches a link back to the original item in the Linear issue.

Fencer receives Linear issue update events through a webhook. When a linked Linear issue moves to a state named Done, open linked vulnerabilities and vulnerability groups move to Ready for verification, and new or under-investigation detections move to True Positive. When it moves to a state named Canceled, linked vulnerabilities and vulnerability groups are ignored with the reason Will Not Fix, and new or under-investigation detections move to False Positive.

Usage / Configuration

Connecting Linear

Navigate to Admin > Integrations in your organization.
Click the Linear card, then click Continue.
Click Connect Linear. You are redirected to Linear’s OAuth authorization page. Authorize Fencer to access your workspace.
After authorization, you are redirected back to Fencer. The integration is now active, and identity sync begins automatically.

Creating issues from vulnerabilities

Open a vulnerability detail page.
In the Tracking row, click Linear. The Track in Linear dialog opens on its Create tab.
Select a Team, and optionally set an Assignee, Label, and Project. The dialog starts with your saved defaults. When the vulnerability’s assignee has a linked Linear account, that person is the starting Assignee. When the team has a label named “Security”, it is the starting Label. To keep a value you changed for the next issues, select Make this my default below the field. Fencer saves assignee, label, and project defaults for each team.
The Title and Description are auto-generated from the vulnerability details if you leave them blank. Adjust as needed.
Click Create issue. The Linear issue identifier is saved on the vulnerability, and an attachment linking back to Fencer is created on the issue.

Creating issues from detections and secrets

The same workflow applies to detections and secrets. Open a detection or secret detail page, click Linear, and complete the form.

Linking existing issues

Instead of creating a new issue, open the Link tab of the Track in Linear dialog, search for an existing Linear issue under Issue, and click Link issue. To unlink, open the menu next to the linked issue identifier on the detail page and click Unlink.

Bulk operations

From the vulnerabilities (including grouped views), detections, or secrets lists, select multiple items and choose Linear from the bulk actions bar to:

Create Linear issues — Single for one issue covering every selected item, or One for each for an issue per item.
Link selected items to a single existing Linear issue.
Unlink selected items from their Linear issues.

Opening issues automatically

An automation opens Linear issues for you when a rule matches. You need permission to edit automations (organization admins have it). For the full reference, see Automations.

Go to Settings > Automations and click New automation. Pick a starter such as Critical and high vulnerabilities to an issue, Leaked secrets to an issue, or SLA breaches to an issue, or click Start from scratch.
Under When this happens, choose the trigger and add conditions to narrow it. Linear issues can be opened from New vulnerability detected, Vulnerability status changed, Vulnerability SLA alert, Vulnerability deferral overdue, and Security detection; the other triggers in the list only offer Notify.
Under What to do, choose Create a ticket in Linear and fill in the Team (required), and optionally the Project, Label, State, and Assignee.
Under How to file, choose Grouped (one issue per run, listing every matching vulnerability) or Per vulnerability (one issue each).
Under More settings, Skip vulnerabilities that already have a Linear issue (on by default) prevents duplicates, and Max vulnerabilities per run (25 by default, at most 100) caps each run. Vulnerabilities above the cap are skipped and listed in the run log.
Optionally choose Assign to the vulnerability owner; the Assignee then becomes the Fallback assignee for owners Fencer cannot match.
Click Preview to see the issues the automation would open, then click Save rule. Use Runs to see what each run filed.

Each issue ends with a footer naming the automation that opened it. If Linear is disconnected, the rule still runs but its ticket action fails with “Linear is disconnected. Reconnect Linear to resume delivery.”, and the rule shows Needs attention in the list until you reconnect Linear.

Severity-to-priority mapping

Fencer sets the Linear priority from the item’s severity automatically (for several items in one issue, the highest severity):

Fencer Severity	Linear Priority
Critical	Urgent (1)
High	High (2)
Medium	Medium (3)
Low	Low (4)
Info	No Priority (0)

Bidirectional status sync

Once a Linear issue is linked, status changes in Linear automatically update Fencer:

Linear Status	Fencer Vulnerability Effect	Fencer Detection Effect
Done	Open ones move to Ready for verification	True Positive
Canceled	Ignored with reason Will Not Fix	False Positive

Fencer verifies each webhook delivery’s signature and rejects deliveries older than 60 seconds.

Identity sync

When you connect Linear, and daily after that, Fencer syncs workspace users into the identity management module when your plan includes it. Users are mapped as vendor identities with their name, email, active status, and role (admin or member).

Disconnecting

Navigate to Admin > Integrations.
Find the active Linear connection and click Remove, then confirm.
Fencer revokes the OAuth access token and removes the connection. The associated vendor record is also cleaned up.

Examples

Creating an issue from a critical vulnerability:

Open the vulnerability detail page for a critical finding such as “SQL Injection in login endpoint.”
In the Tracking row, click Linear.
Fencer generates the title and a detailed description including severity, repository, location, security standards, and remediation steps, and sets the priority to Urgent.
Select your engineering team, assign to a developer, and click Create issue.
The issue appears in Linear with a Fencer attachment. When the developer marks it as Done in Linear, the vulnerability automatically moves to Ready for verification in Fencer.

Troubleshooting

“Linear integration not configured” error — Ensure the Linear integration is connected in Admin > Integrations. Only administrators can set up the connection.
Issues not syncing back — Only state changes to a state named “Done” or “Canceled” trigger sync. Completed or canceled states with other names are not synced.
OAuth token expired — If the connection shows an Issue status, try disconnecting and reconnecting the integration to refresh OAuth tokens.
“Reconnect Linear for an improved Automations experience.” — Reconnect so Linear shows the Fencer app, not the person who connected Linear, as the creator of issues.
Bulk create partially fails — If some issues fail during bulk creation, Fencer reports the count of successes and failures. Check that your Linear workspace has not hit API rate limits.