Ticket tracker write-back
Connect a project to Jira or Linear once. From then on, every ingested run posts its pass/fail evidence as a comment on the ticket named by the case that proved it — no CI step to configure.
Linear and Jira directories are where this job already lives; the comment they would see is the same shape as the public case file.
1. Connect a tracker
- Open a project's Integrations tab and click Connect Jira or Connect Linear.
- You'll be sent to that vendor's own consent screen — ReleaseTwin never sees your Jira or Linear password, only the OAuth grant you approve.
- The connection resolves automatically: for Jira, the single Atlassian site your grant covers; for Linear, your workspace. Nothing to pick.
- A project can have a Jira connection, a Linear connection, both, or neither. If both are connected, Jira is used.
2. How a ticket is found
Write-back reads the same oracle.locator field a case file already declares — no new field to add. A locator matching the tracker's native issue-key shape (e.g. PROJ-123) is resolved against the connected site or workspace.
- A locator that doesn't match this shape is skipped, not treated as an error.
- A locator that matches the shape but doesn't resolve to an existing ticket (wrong key, deleted ticket) is also skipped — same non-error treatment.
- A genuine delivery problem (expired credential, rate limit, vendor outage) is recorded as failed. Either way, write-back never changes a run's own pass/fail result or blocks the CI job that uploaded it — posting happens after the run is already recorded, off the critical path.
Every attempt — posted, skipped, or failed — shows up in the project's write-back history.
3. Linear only: request a re-verification from the ticket
On a project with Linear connected, @-mentioning, assigning, or delegating an issue to the ReleaseTwin agent replies within seconds with an acknowledgment, and records the request on the project's dashboard under Rerun requests — a single place to see every re-verification ask across a project, whoever filed it and whichever ticket it came from.
This records and acknowledges the request; it does not trigger a re-run yet. Turn it on from a connected project's Integrations tab with Enable rerun requests, a one-time re-authorization separate from the initial Linear connection.
4. What happens if access is revoked
Neither Jira nor Linear's standard OAuth app model pushes a signal when a customer revokes access from their own account settings — that's a property of a plain OAuth app (as opposed to an installed marketplace app), not a gap in this integration. ReleaseTwin instead renews the connection's access token in the background before it expires; if the vendor rejects that renewal, the connection is marked revoked and the dashboard shows it needs reconnecting. There can be a short window — bounded by that background check's cadence — between a revoke and ReleaseTwin noticing it.
Plans
Jira write-back and Linear write-back are each their own entitlement, available on the Team plan and above — connecting one doesn't require the other. See pricing.