What you need
- Your Jira Cloud site URL (for example https://acme.atlassian.net)
- The account email the API token belongs to
- An Atlassian API token for that account
- The project key tickets should come from (for example OPS)
- A trigger label — the default is ai-fix, but you can pick anything that doesn't collide with your existing labelling scheme
Set it up
- Connectors → Add connector → Jira
- Enter the site URL, account email, project key, and trigger label, and paste the API token
- Click Test connection — it shows the account it authenticated as and the project it found
- Copy the webhook URL from the connector's card and add it to Jira (see Getting started)
The webhook is a doorbell, not a delivery
The webhook payload Jira sends is never trusted for its content — only the ticket's key is read from it, as a lookup. Before deciding whether to act, Noviqent DevOps re-fetches the real, current ticket through your own Jira credentials and checks its real, current labels. A stale or spoofed payload can't trigger a fix attempt on a ticket that doesn't actually carry the label.
What gets read, and what gets written
Before reasoning, related tickets in the same project are searched — the "has this happened before?" half of context gathering. Only the summary, status, and key of matches are used.
The one write: a single comment posted back onto the ticket once the pipeline finishes, containing the root cause, the PR link if one was opened, and whether its CI passed.