Integration
Sitejar Linear integration
The Sitejar Linear integration turns website scan findings into Linear issues in the team you choose, one issue per finding and never a duplicate: sending a finding again adds a comment to the issue it already has. Each issue carries the rule, the severity, the pages it was found on and the suggested fix, its state shows on the finding in Sitejar, and only a scan that no longer detects the problem marks it fixed.
On Pro and above.
What the Sitejar Linear integration does
Sitejar scans a site in a real browser for accessibility (WCAG 2.1 AA), security, privacy, deceptive design, technical quality and SEO, and tracks each problem from scan to scan. This integration carries those findings to where your team plans its work, written so whoever picks one up can start without opening Sitejar.
- One issue per finding. Sending it again adds a comment instead of a second issue.
- The issue's state, read back from Linear, shows on the finding.
- A default team for the workspace, and its own team for any site that needs one.
- Whole reports in one send: a Linear project in the same team, with each finding's issue inside it.
Who the Linear integration is for
Teams that already plan their work in Linear and want website problems in the same queue as everything else. If your engineers live in Linear cycles and triage, findings arrive as ordinary Linear issues in the team you choose, with your workflow states, labels and estimates applied the way you apply them to anything else. It suits agencies handing client fixes to a delivery team, and developers who would rather get an issue with a selector and a fix than a PDF.
Send accessibility issues to Linear
Accessibility is the most common reason teams send findings, but any finding can go: a missing security header, a tracker that loads before consent, a broken link.
Turn a new scan into a backlog
Send a whole report and Sitejar creates a Linear project in the same team, with each finding's issue inside it, most severe first, filtered by severity and with or without Needs review findings. Send the same report again later and only the findings not yet sent are added.
Send just what fits this sprint
Select a handful of findings on the Findings page, or open one finding, and send only those. The rest stay in Sitejar until you are ready.
Keep each client's work in its own team
Give a site its own destination, and its findings go to that team while everything else goes to the default. On Agency Plus, a client can have a destination too: a site's own wins over its client's, and its client's over the default.
How to connect Linear to Sitejar
- Sign in to Sitejar as an Owner or Admin of the workspace and open Settings, then Integrations.
- On the Linear card, choose "Connect Linear". If your plan does not include Linear, the card says "Not on your plan" instead.
- Linear opens its own consent screen. Check that it names the right Linear workspace, then approve access.
- Back in Sitejar, the card says "Connected to" followed by your Linear organization's name. Under "Tasks go to", choose the team new issues go to by default.
- Optional: under "Give a site its own destination", pick a site and a team, then choose "Add".
A workspace has one Linear connection, and connecting again replaces it.
How to send findings to Linear
Anyone whose role can manage findings (Owner, Admin or Editor) can send them, three ways:
- On the Findings page, select findings and choose "Send to Linear" in the bulk actions bar, or choose "Create tasks" and pick Linear under "Send to". Up to 50 at a time.
- On one finding, use "Send to Linear" in its Task section, which then links to the issue.
- On a report, choose "Send report to Linear" in the Next steps panel ("Send report to a task tool" when more than one is connected), pick the severities, and send. Up to 100 issues at a time.
What Sitejar sends to Linear, and what it stores
What a Linear issue from Sitejar contains
The title names the dimension, the severity, the rule, the page count and the site: [Accessibility][High] Form field missing a label (12 pages) | example.com.
The body carries the confidence label (Confirmed, Likely or Needs review), how many instances on how many pages and the scan date, a CSS selector, the WCAG success criterion where one applies, the first 20 page urls, the suggested fix and its code when one exists (or "No AI fix yet"), and a link back to the finding. It never contains evidence captured from your pages or their content. Linear renders the body as Markdown, so the selector and any suggested code read as code.
Permissions Sitejar asks for in Linear
Sitejar connects through OAuth 2.0 and asks Linear for its read and write scopes. It uses them to list your teams, create issues (and, for a whole report, a project), add comments, read an issue's state and, if you turn it on, change that state.
Linear access tokens expire. Sitejar renews them with the refresh token Linear issues and saves the new pair, so the connection keeps working without you signing in again.
What Sitejar stores about your Linear connection
Sitejar stores the Linear access token and refresh token, your Linear organization's name for the card, your Linear workspace's url key, and the last error Linear returned. Credentials are encrypted with AES-256-GCM and never sent to your browser. For each issue it created, Sitejar keeps the issue's id, url, last state and when it last checked. Sitejar keeps no personal data from Linear. The label on the card is your organization's name, not a person's, and Sitejar never reads members, comments or issues it did not create.
Disconnecting empties the stored credentials at once, and the issues already created stay in Linear. To revoke the grant on the Linear side too, remove Sitejar in Linear's own settings.
What happens in Linear after the next scan
The sync runs one way: a scan can move an issue, but closing an issue never marks a finding fixed. Only a scan that no longer detects the problem does, so a issue closed by mistake or before the deploy cannot flatter your scores.
When a linked issue is shown in Sitejar, Sitejar reads its state from Linear, at most once every 10 minutes. The finding shows the state by its name in your workflow, such as In Progress, and treats the issue as closed when Linear says its state is completed or canceled. If Linear answers with an error, the last known state stays. Issues deleted in Linear show as Removed, and one closed while the latest scan still finds the problem shows "Reopened: closed in the tool, still detected in the latest scan."
On Business and above, each completed scan adds one comment to every linked issue: "Still detected in the Sitejar scan of 3 November 2026." or "Not detected in the Sitejar scan of 3 November 2026. A scan, not this task, confirms a fix."
On Agency Plus, you can turn on "Move tasks after each scan" on the Linear card. Issues whose finding is not detected then move to the team's first completed state, and those whose finding comes back move to the team's first unstarted state. It is off until you turn it on.
Which plans include the Linear integration, and its limits
Linear is on Pro and above. Whole-report sends and after-scan comments are on Business and above, and automatic moves and per-client destinations are on Agency Plus. To see everything each plan includes, compare plans on the pricing page.
- One Linear connection per workspace.
- Up to 50 findings per send from the findings list, and up to 100 issues per whole-report send. Send the report again for the rest.
- The first 100 teams in your Linear workspace are offered as destinations.
- A whole-report project name is cut at 80 characters, and its description at 255, which are Linear's own limits.
- Dedupe belongs to the connection: findings sent through a connection you have since replaced go out as new issues.
Troubleshooting the Linear integration
"That connection link expired or was already used"
The link Linear sends you back with works once, within 10 minutes of choosing Connect. Choose "Connect Linear" again and finish without a long pause.
"Choose where Linear tasks go for this site first"
No destination applies to that site yet. Choose a default under "Tasks go to", or give the site its own.
The card shows "Last attempt" with an error from Linear
That is what Linear answered on the last call. "Linear answered 401" or "403" usually means the access was revoked or the connected account lost access to that team: connect again, or choose another team. "Linear answered 404" usually means it was deleted.
The card says "Linear refused to renew the connection"
Sitejar tried to renew Linear's expiring access token and Linear said no, usually because the access was revoked on the Linear side. Choose "Disconnect", then "Connect Linear" again. Findings you sent before stay in Linear.
Moving issues after a scan fails with "The Linear team has no completed state"
Automatic moves use the team's own workflow: the first state of type completed for a fix, and the first unstarted state to reopen. Add those state types to the team's workflow in Linear, or turn "Move tasks after each scan" off.
Linear integration FAQ
Does sending a finding to Linear twice create two issues?
No. Sitejar links each finding to the issue it created. Sending the same finding again through the same connection adds a dated comment with its current details to that issue.
Does closing the Linear issue mark the finding fixed in Sitejar?
No. Sitejar shows the issue's state, but a finding counts as fixed only when a scan no longer detects the problem. If the issue is closed while the latest scan still finds it, the finding says it was reopened.
What does Sitejar store from Linear?
The credentials for the connection, encrypted with AES-256-GCM, your Linear organization's name, and for each issue it created, its id, url and last known state. Disconnecting deletes the credentials at once.
Which plan do I need for the Linear integration?
Linear is on Pro and above. Whole-report sends and after-scan comments are on Business and above, and moving issues automatically after a scan is on Agency Plus.
Can Sitejar put the Linear issues in a project?
Yes, when you send a whole report. Sitejar creates one Linear project for that scan, in the team the issues go to, and puts each finding's issue in it. Findings sent one at a time or from a selection go to the team without a project.
Related integrations
Last updated . Linear and the Linear logo are trademarks of Linear Orbit, Inc. Sitejar is not affiliated with or endorsed by Linear Orbit, Inc.