Screendog files Jira issues directly via the REST API.
Connect Jira once with an Atlassian API token, your site URL, and a project key. Every recording becomes a fully-structured Jira issue — summary, wiki-flavoured description, issuetype, severity-mapped priority, labels, and recording link — created server-side via `POST /rest/api/2/issue`.
| Capability | Status |
|---|---|
| Live REST integration | Yes — `POST /rest/api/2/issue` |
| Atlassian API token (id.atlassian.com) | Yes — Basic auth with email + token |
| Project key + site URL stored per workspace | Yes — never returned to the browser |
| Severity → Jira priority mapping | Yes — critical→Highest, high→High, medium→Medium, low→Low |
| Type → Jira issuetype mapping | Yes — bug/incident → Bug; doc/demo/pr → Task |
| Incident template support | Yes — incident summary, impact, timeline, mitigation, follow-ups all land in the Jira description |
| Atlassian Connect / OAuth 3LO | No — API token only today |
| Two-way sync (Jira status → recording) | No — file-and-forget by design |
How it works
In `/<workspace>/settings`, paste your Jira email, an Atlassian API token, your site URL (`https://your-org.atlassian.net`), and a project key (e.g. `ENG`). When you finish a recording, click File to Jira — Screendog calls the REST v2 endpoint server-side with Basic auth, sets summary + wiki-flavoured description + issuetype + priority + labels, and returns the new issue's URL.
What lands in Jira
Summary (title), wiki-formatted description (repro steps, expected/actual, browser/OS metadata, recording share link, transcript excerpt), issuetype mapped from the recording type (bug/incident → Bug; doc/demo/pr → Task), priority mapped from severity (critical → Highest, high → High, medium → Medium, low → Low), and a single auto-derived label per recording type (bug → `bug`, incident → `incident`, doc → `documentation`, demo → `sales`, pr → `code-review`). Labels are sanitized to `A-Za-z0-9_-` because Jira rejects whitespace in label values.
Incident postmortems land cleanly
When you file an incident-type recording, the structured incident summary, customer/business impact, timeline, mitigation, and follow-up actions are all serialized into the Jira description as a structured block. The on-call recording link is embedded so the postmortem author has the source evidence one click away.
Resilience: priority-field-not-configured
Some Jira projects do not have a Priority field configured on their issue screen. If Screendog's first request gets rejected for that reason, it transparently retries without the priority field and surfaces the issue successfully.
Security model
Your API token is stored only in the workspace's `tenant_integrations` row. List endpoints expose `configured: true` plus a non-sensitive hint (`PROJECTKEY · your-org.atlassian.net`); the raw token is never returned over the wire. Token format is validated at save time so misconfigurations fail fast.
Frequently asked
Where do I get the Atlassian API token?
Visit id.atlassian.com/manage-profile/security/api-tokens, create a token, and paste it into Screendog along with the email you used to log into Atlassian.
Does Screendog support Jira Server / Data Center?
Today only Atlassian Cloud (`*.atlassian.net`) is supported. Self-hosted Jira Server / Data Center is a known gap.
Can I file to multiple projects from one workspace?
One project key per Screendog workspace today. For multi-project filing, create additional Screendog workspaces.
Will the issue close back into Screendog when it ships?
No two-way sync today. Status changes happen in Jira; Screendog records the URL of the issue you filed.
What happens if my Jira project rejects the priority field?
Screendog automatically retries the request without the priority field. Some Jira projects scope priority off the create screen; the issue still files successfully without it.
Try Screendog free.
5 recordings on the free trial. Real Linear, GitHub, Notion, Slack, and Jira filing. No credit card.
Start a workspace — free