Ticket integrations

What it is

From any finding, “Create ticket” pre-fills the title, description, severity, the verbatim PoC excerpt, and a link back to the cinematic replay, then opens it in the chosen tracker. The operator’s team picks up a ticket that already contains everything needed to triage.

What it produces

• A ticket in the configured tracker (Jira / Linear / GitHub Issues) with:
  • Title: [critical] {finding-kind} on {target.value}
  • Body: severity / affected URL / verbatim PoC exchange / replay link / methodology summary
  • Labels / components: mapped from finding kind + severity
• An entry in the per-finding “Tickets” history so duplicates are prevented and the link stays visible

What to use it for

• Operator handoff: “this is for the platform team. Jira goes here”
• Triage close-out: ticket links the finding, finding links the replay, replay shows the actual PoC
• Cross-team workflow: a finding can be ticketed multiple times to multiple trackers (one for security, one for the team that owns the asset)

Why it matters

The slowest part of a security program is the handoff between “we found something” and “the right team is working on it.” A ticket that arrives with title, severity, PoC, and replay link pre-filled makes that handoff zero-cost.

Why it’s valuable

• No copy-paste. The body is filled from the finding payload, no risk of stale data or summary drift.
• Replay link inside the ticket. Whoever opens the ticket can verify the finding themselves without an Umbra account.
• Multiple trackers per workspace. Different teams use different tools; both get the same ticket payload.

How to use it

1. Admin → Integrations → Add ticket integration. Configure the tracker (Jira host + project key, Linear team / GitHub org+repo, etc.) with the integration’s API token.
2. On any finding, click Create ticket: pick the integration, review the pre-filled body, hit submit.
3. The created ticket URL is stored on the finding so it doesn’t get re-ticketed accidentally.