Linear
Reviews arrive as issues in the team that owns the vendor, with an assignee, a cycle and a due date already set. Closing the issue signs off the review, so there is one place a decision is recorded rather than two.
- Category
- Ticketing & work
- Auth method
- OAuth 2.0 or API key
- Direction
- Two-way
- Sync frequency
- Real time
- Scopes requested
- 4
- Available on
- All plans
- Maintained by
- Urengi
What the Linear integration does
Three jobs, shaped the way a Linear team already works.
An issue per review
The issue lands in the team you mapped, with the tier as a label and the evidence checklist in the description. Re-running the review updates the same issue.
Cycles carry the deadline
A review with a certificate expiry gets a due date and drops into the cycle that ends before it. Renewals compete for capacity like everything else, which is the point.
Done means signed off
Moving the issue to Done records the sign-off against the review, with the assignee as the approver. One decision, one record.
Exactly what Urengi can see
Four scopes on the teams you name. Urengi cannot see a team you did not select.
Urengi reads
- Team and project names
- Workflow state names
- Member display names and emails
- Issues Urengi itself created
Urengi writes
- Review issues in the selected teams
- Labels, assignees and due dates on those issues
- Comments carrying evidence updates
Urengi never touches
- Issues in teams you did not select
- Attachments or their contents
- Documents, initiatives or roadmaps
- Anything after you revoke the key
Connect it in four steps
One authorisation, one field mapping, and a test sync you run yourself.
01
Authorise the connection
Open Linear from this page and approve the scopes listed above — OAuth in a browser tab, or a scoped API key you paste. An admin approves them once.
02
Choose what syncs
Pick the projects, spaces or accounts Urengi should watch. Narrow is fine to start with; widening it later does not re-authorise anything.
03
Map your fields
Match owners, cost centres and tiers to what Urengi already tracks. Defaults arrive pre-filled from the first sync, so most teams change nothing.
04
Run a test sync
Pull one record and check it landed on the right review. The audit entry confirms the mapping before a real vendor is touched.
Your token, your rules.
Urengi stores the Linear token encrypted at rest under a per-tenant key and never replays it outside the scopes you approved. Revoke the app in Linear and every Urengi write stops within seconds — the audit log keeps the history, the connection simply ends.
Read the security statement- SOC 2 Type II
- audited annually
- Per-tenant keys
- no shared secrets
- Revocable in Linear
- one click, no ticket
- EU or US residency
- chosen at signup