Ticketing
TrustVendor + Linear
Linear is the modern issue tracker used by product and engineering teams. TrustVendor routes vendor risk signals to Linear issues, keeping vendor risk visible in the same tool your team already lives in.
How data flows
Signals from TrustVendor are pushed to Linear via the Linear API, creating issues in the team and project you configure.
How to set up
- 1 Connect TrustVendor to your Linear workspace from Settings > Alerting.
- 2 Authorize the connection and select a team.
- 3 Configure signal routing rules by severity and vendor group.
Common questions
Does TrustVendor support Linear triage workflows?
Issues are created with the label and priority you configure. Triage automation within Linear applies as it would to any other issue.
How does TrustVendor signal severity translate to Linear issue priority?
TrustVendor maps critical to Urgent, high to High, medium to Medium, and low to Low in Linear. The mapping is configurable in TrustVendor's alerting settings if your team uses a different Linear priority convention. The issue description always includes the signal type, the affected vendor, a summary of the underlying claim, and a direct link to the TrustVendor evidence drawer.
Can TrustVendor route signals to different Linear teams based on vendor type?
Yes. You can define routing rules in TrustVendor that send signals for infrastructure vendors to your platform team's Linear project and signals for SaaS vendors to your security team's project. Rules can filter on vendor group, data class handled by the vendor, or signal type, and multiple rules can apply to the same signal.
Does resolving a TrustVendor signal automatically close the corresponding Linear issue?
When a signal transitions to resolved status in TrustVendor — either manually or because the underlying condition is no longer detected — TrustVendor updates the Linear issue state to the completed state you configure during setup. This keeps your Linear backlog clean without requiring your team to manually close vendor risk issues once the underlying problem is addressed.
Is there a way to prevent TrustVendor from creating duplicate Linear issues for the same vendor finding?
TrustVendor's signal deduplication ensures that a single underlying finding maps to one signal, so only one Linear issue is created per unique signal. If a monitored condition changes in severity — for example, a high signal is re-evaluated as critical — TrustVendor updates the existing Linear issue priority rather than opening a duplicate.