Ticketing (Jira, Linear, ServiceNow, …)
Ticketing · merge_link · Daily
Unified ticketing integration via Merge.dev. One connector reaches 25+ ticketing platforms; customers pick their provider during setup. Pulls open + closed ticket counts and recently-resolved change-management tickets for SOC 2 CC8.1 evidence — complements the direct Jira connector by extending coverage to Linear, ServiceNow, Asana, Monday, Trello, and the long tail.
- Authentication
- merge_link
- Sync cadence
- Daily
- Stale threshold
- Every 2 days
- Category
- Ticketing
Evidence this connector produces
Every sync writes typed evidence rows linked to the controls below. Evidence is immutable once attached to an approved assessment, fingerprinted for de-dup, and surfaced in the control coverage calculation on your dashboard.
How to connect
Click Connect to launch the Merge Magic Link flow. You'll pick your ticketing system, sign in, and authorize read-only access.
- 1Pick your ticketing provider in Merge Link
Merge supports Jira (server + cloud), Linear, ServiceNow, Asana, Trello, ClickUp, Monday, Pivotal Tracker, Shortcut, GitLab Issues, and more.
- 2Authorize read-only access
Merge handles the provider's OAuth flow. Scopes are read-only — we never create, modify, or delete tickets.
- 3Sync starts immediately
First pull collects open + closed ticket counts and the last 30 days of resolved tickets. Daily syncs thereafter.
Security model
Every connector ships behind the same auditor-grade primitives — not just RBAC config, but architectural enforcement.
Tokens, client secrets, and service-account keys are encrypted under a per-tenant AWS KMS data key. The plaintext is never persisted, never logged, and never leaves the FastAPI process boundary.
Every Connection, ConnectorRun, and emitted Evidence row carries an organization ObjectId. The scheduler never iterates without an org-scoped filter; cross-tenant evidence bleed is impossible at the data layer.
Connect, sync, sync-failure, re-auth, and revoke each write a row to the immutable AuditLog. The full lifecycle is reconstructable for any examiner.
Revoking a connection sets deletedAt and clears the encrypted credential blob, but the historical evidence + sync log stays queryable for the retention window. Auditors can still trace what was attested when.
If this connector hasn't synced in Every 2 days, control coverage degrades automatically and an alert fires. Auditors don't trust stale evidence — neither do we.
We request the minimum read-only scopes needed for the listed evidence. No write scopes, no admin scopes, no scopes outside the documented set.
Ready to connect Ticketing (Jira, Linear, ServiceNow, …)?
Connect from Settings → Integrations — typically under 5 minutes. Or talk to us first.