Home / Integrations / Jira

Jira Cloud — one issue per feedback item

File a Jira Cloud issue for each new Feedback DevTools item through a destination rule: summary, what to change, page, file:line and a link back. Uses an Atlassian account email and API token. Not a Jira app; no status sync back from Jira.

What it does

One issue per new item. Each item that matches the destination's type and urgency filters becomes one issue in the Jira project you pick, as a Task, Bug, or Story.
Fields filed: the summary is the item's title; the description holds what to change, the expected behavior, the page URL, the source file:line when the SDK mapped the element, the screenshot link, and a link back to the item. Labels feedback-devtools and fd-<item id> are added.
Retries. Delivery goes through the same routing outbox as Slack and the signed webhook, so a Jira outage is retried with backoff and never slows down feedback collection.
Safe test. Send test checks that the email, token and project key work without creating an issue.

How to connect

Create an API token for your Atlassian account at id.atlassian.com/manage-profile/security/api-tokens.
In the FDT project dashboard: Project → Settings → Destinations → Add → Jira Cloud. Enter your site address (https://your-team.atlassian.net), the account email, the project key (the WEB in WEB-123), and the token.
Press Send test, then Save destination.

Honest limits

Jira Cloud only (*.atlassian.net). Jira Server and Data Center are not supported.
Not a Jira app or OAuth integration: issues are created as the account that owns the token.
One-way. Moving or closing the Jira issue does not change the item in FDT.
If Jira creates the issue but its answer is lost on the way back, a retry can file a duplicate. The fd-<item id> label makes it easy to spot.