Jira

The Jira integration lets Cendriix read tickets as the input to a run and write status and comments back as the run progresses. This guide covers connecting Jira and the ticket-to-run flow.

Overview

Cendriix connects to Jira Cloud through OAuth. Once connected, any run can take a ticket key as input; the orchestrator reads the summary, description, and acceptance criteria and uses them to plan the change.

Connecting Jira

cendriix workspace connector add \
  --provider jira --site acme.atlassian.net

This opens the Atlassian OAuth consent screen. Cendriix requests read and write scopes for Jira work items; approve the consent and the connector turns active. Jira Data Center (self-hosted) is supported via a personal-token connection rather than OAuth.

How tickets become runs

Pass a ticket key to any workflow that declares a ticket input. The orchestrator fetches the issue, extracts the acceptance criteria, and treats them as the definition of done for the run.

cendriix run ship-from-ticket --ticket JIRA-3421

Status transitions

As a run moves through its lifecycle, Cendriix transitions the linked Jira issue and posts comments at key milestones, when a pull request opens, when a preview deploys, and when the change ships. The transition names map to your project's workflow, so a run that ships moves the ticket to whatever your board calls "done".

Automatic triggers

Beyond manual cendriix runinvocations, you can configure a trigger so that moving a ticket into a designated status, for example, "Ready for Cendriix", automatically starts a run. Configure triggers from the Connectors page in the dashboard.

Next steps