Docs

Jira ​

Open Jira change tickets for gated releases and move them as they ship.

Open change tickets for gated releases and move them as they ship. Open the Jira card on the Integrations page to sign in with Atlassian or paste a token.

Change tickets ​

Beta, early access. Flag: jira.

Terminal
echo "$JIRA_TOKEN" | bumpkit integrations connect jira --set site=acme --set email=bot@acme.com --set project=OPS --api-key -
bumpkit integrations authorize jira

Over the API, send the settings and the token together in settings, for example {"settings": {"site": "acme", "email": "bot@acme.com", "project": "OPS", "api_token": "…"}}. Bumpkit checks the credentials before saving. Failed deliveries are retried automatically and listed on the Jira card, where an owner can retry them with bumpkit integrations deliveries retry jira DELIVERY_ID. The integrations_connect, integrations_deliveries_list and integrations_deliveries_retry MCP tools do the same.

Opens a Jira change ticket when the gate asks for approval or fails, and moves it as the release progresses.

Setting Required Meaning
site yes Your Jira Cloud site: acme or https://acme.atlassian.net
email yes The Atlassian account the API token belongs to
project yes The project key, like OPS
issue_type no Default Task
approve no The transition to run when the gate passes, like Approved
ship no The transition to run when the release reaches production, like Done
rollback no The transition to run when production is rolled back, like Rolled back
api_token yes An Atlassian API token (the CLI's --api-key)

How tickets move:

  • Gate needs approval or fails: Bumpkit opens a ticket with the gate's reasons and an evidence link. If the pull request title, branch or a commit names an existing issue in the project (like OPS-42), Bumpkit links that issue instead of creating one. Later decisions add comments.
  • Gate passes: the ticket runs the approve transition. A break-glass override opens the ticket already approved, marked as an emergency change.
  • Deploy to production (production, prod or live): tickets for that commit run ship. A production deploy with no ticket gets one, opened as shipped. Earlier shipped tickets are noted as superseded.
  • Rollback (production redeployed to an earlier commit): shipped tickets run rollback.

When a transition isn't set or isn't available from the issue's status, Bumpkit adds a comment instead.

↑↓ to move, Enter to open