đ§Ş This feature is available as part of a private beta.
The Linear integration allows you to create Linear issues from Intigriti submissions and keep them updated as submissions change. Connect your programs to the relevant Linear teams so your engineering team can track remediation in its existing workflow.
đSubscriptions: Starter, Core, Premium, Enterprise
Create a Linear connection
âď¸Roles: Company Admin
Before configuring a program, create a connection between your Intigriti company and your Linear workspace. A Linear workspace admin must authorize the connection. Intigriti is installed as an app in your workspace, so issues and comments are created by the Intigriti app rather than by the person who connected it.
Go to Admin > More > Integrations.
Find Linear and click Open overview.
Click Add connection.
Give the connection a recognisable name using the edit icon next to its name. You can optionally upload a logo.
Click Connect.
Authenticate in Linear and authorise the connection to the intended workspace.
Once connected, you can reuse the connection across multiple programs. The connections overview includes Open details to view a connection and View integrations to see the program integrations that use it.
Configure Linear issues for a program
âď¸Roles: Company Admin, Program Admin
Open your program and go to More > Integrations.
Find Linear and click Open overview.
Click Add integration.
Give the integration a recognisable name. You can optionally upload a logo.
Under Linear details, select your Linear connection.
Select the Linear team where issues should be created.
Optionally select a Project and Labels to apply to issues.
Configure Issue creation and Synchronisation as described below.
Click Activate.
The program overview shows each integration's status, team, issue creation mode, and connection. Click Integration details to review its configuration.
â ď¸Beware: Keep the selected team, project, labels, and mapped workflow states available in Linear. Removing them can prevent issues from being created or updated.
Issue creation
Choose whether issues should be created automatically or manually.
Automatically: Create an issue when a submission reaches the selected stage: Submitted, Validated, or Accepted. Use the Severity selection to configure which severities are eligible for automatic issue creation.
Manually only: Create issues manually from a submission rather than automatically when it reaches a selected stage.
The automatic configuration lists the severities None, Low, Medium, High, Critical, Exceptional, and Undecided.
đĄNote: The settings also allow manual issue creation when automatic creation is selected. Choose automatic creation for predictable routing, or manual creation when your team needs to decide which submissions to send to Linear.
Priority synchronisation
Enable Priority to set the Linear issue priority based on the submission severity and update it when the severity changes.
For each submission severity, choose the corresponding Linear priority. You can select Don't set where you do not want to assign a priority.
For example, you could map High submissions to High priority, and Critical or Exceptional submissions to Urgent priority. Review the mappings to make sure they match your team's remediation process.
Status synchronisation
Enable Status to move the Linear issue to a selected workflow state when the submission status changes.
Choose a Linear workflow state for each relevant submission status or close reason. Select Don't change where a submission change should not move the Linear issue.
The settings include Triage, Pending, Accepted, Archived, and separate mappings for closed submissions, including Resolved, Duplicate, Accepted risk, Informative, Out of scope, Spam, and Not applicable.
â ď¸Beware: When priority or status synchronisation is enabled, a submission change can overwrite the linked issue's priority or workflow state with the configured value. Changes made directly in Linear are not synchronised back to Intigriti.
Messages & attachments
Under Messages & attachments, select which sources of submission messages and attachments should be posted as comments on the Linear issue:
Researchers
Company members
Intigriti triage
Platform events
đĄNote: Internal messages are not synchronised to Linear. Review which other messages and attachments you share before activating the integration, and make sure access to the Linear team is appropriate for the submission information.
Activity comments
Under Activity comments, choose which submission changes should add a comment to the Linear issue:
Status updated
Severity updated
Retest updated
Activity comments and field synchronisation are separate settings. For example, you can keep Severity updated comments enabled without updating the issue's priority.
Troubleshooting
A connection or team is unavailable
Check that the company-level Linear connection is connected to the intended workspace. Select the Linear connection before selecting a Linear team. Verify that the app still has access to the workspace and the required team.
If the expected team, project, or label is missing, ask your Linear administrator to check access and confirm that it still exists.
Issues are not created automatically
Check that:
The program integration is active.
Automatically is selected under Issue creation.
The submission reaches the configured stage and meets the selected severity criteria.
The selected connection, team, optional project, and labels remain available in Linear.
â ď¸Beware: Choose no more than one label from the same Linear label group. Selecting multiple labels from a single group can cause Linear to reject issue creation.
If the issue persists, use Request support on the integration settings page or contact technical support via the chat.
The issue priority or status does not change
Check that the corresponding Priority or Status setting is enabled and that a mapping has been selected. A status mapping set to Don't change leaves the issue's workflow state unchanged.
A change made directly in Linear does not update the submission in Intigriti.
Duplicate issues are created
Review whether more than one integration routes the same program's submissions to the same Linear team. Separate integrations can each create an issue for the same submission.
â ď¸Beware: Deleting and recreating an integration can result in duplicate issues, because the new integration does not recognise issues created by the previous one. Contact support before recreating an integration that already has linked issues.
Best practices
Name connections and integrations clearly so you can distinguish workspaces and destination teams.
Choose an automatic creation stage that matches when your team starts remediation.
Review priority and status mappings with your engineering team before activating the integration.
Enable only the messages, attachments, and activity comments your team needs.
Check program routing before adding another integration to avoid unintended duplicate issues.
Review the configuration after changes to Linear teams, projects, labels, or workflow states.
