Integrations · Jira
A label or a transition starts a change, scoped by project.
DevByte comments back on the issue as the app, and moves it where you map a state. Jira Cloud, over OAuth.
What starts work
Three events, read from the changelog.
A Jira issue scoped by project starts a change, and its webhook is renewed before Atlassian expires it. A label fires on being added, not on every later edit; a status is matched by name, so a Ready for build column needs no id lookup.
- 01
jira.issue.labeleda label is added to a Jira issue
scoped by project_key · label - 02
jira.issue.transitiona Jira issue moves into a status
scoped by project_key · to_status - 03
jira.issue.mentionsomeone mentions @devbyte on a Jira issue
scoped by project_key
What lands back
It writes back as the app: one comment on the issue per milestone, and a status transition where an automation maps one. The issue text arrives as data inside an untrusted-content fence, never as instruction.
What you grant and why
Five scopes, one of them for renewing the webhook.
Jira’s dynamic webhooks are unsigned, so the delivery URL carries a per-installation token and an unrecognised token is refused. A daily job renews the webhook well before its 30-day expiry.
- read:jira-work
- To read the issue that started the change and the projects an automation can be scoped to.
- write:jira-work
- To post the write-back comment and to transition an issue where an automation maps states.
- read:jira-user
- To resolve the person who labelled or commented, so an approval is attributed to a human.
- manage:jira-webhook
- To register the webhook that delivers the events — and to renew it before Atlassian expires it at 30 days.
- offline_access
- To refresh the token, so a connection does not need reauthorising every hour.
The issue that started the change is where the change reports back.One Atlassian site per tenant, the projects named when there is more than one, and disconnecting deletes the webhook without revoking the token — Atlassian offers no revoke endpoint.
Move a card to Ready this week.
Connect the site, scope an automation to a project, and map the status that means go. The pull request arrives with its audit trail.