# Jira

> Deliver backlogs into Jira Cloud, map your workflow statuses once, and let the agents work tickets through your existing pipeline.

_CommerceCopilot documentation · Integrations_

If your team lives in Jira, CommerceCopilot meets you there. Backlogs land as issues in the Jira project you choose, and the agents move work through your existing workflow rather than imposing one of their own.

## What CommerceCopilot uses Jira for

- **Ticket delivery.** Confirmed backlogs from [brief-to-ticket runs](/docs/your-first-brief-to-ticket-project) and discovery proposals are created as issues, with requirements, user stories, and dependency links.
- **Pipeline tracking.** The delivery agents read issue status to know what to pick up next, and update status as work progresses, using your workflow's own statuses.

## Connect Jira

1. Go to **Settings** in the sidebar.
2. Find the **Jira** card and click **Connect**.

![The Jira integration card on the Settings page](/docs/integration-jira.png)

3. Atlassian's authorization screen opens. Approve the requested access (read and write issues, read user info, manage webhooks).
4. If your Atlassian account has access to more than one Jira site, a site picker appears back on the Settings page. Choose the site your team uses.

> **Prerequisite:** an Atlassian Cloud account with access to the Jira site you want to connect. Self-hosted Jira Server/Data Center is not supported.

## Bind a Jira project and map your workflow

Jira setup has one extra step that Notion does not: status mapping. Every Jira workflow is different, so CommerceCopilot needs to know, once, which of your statuses corresponds to each stage of its pipeline.

1. Open the CommerceCopilot project and go to **Settings**, then **Integrations**.
2. Under **Project management tool**, choose **Jira** (a project uses either Jira or Notion, not both), then pick the Jira project and the issue type new tickets should use.
3. Complete the **status map**: for each pipeline stage (analysis, planning, architecture, development, QA), pick the matching status from your Jira workflow.

The delivery agents stay paused on this project until every stage they depend on is mapped. This is a safety measure: an agent that cannot tell "ready for development" from "in review" should not touch your board.

## How tickets look in Jira

Each ticket becomes an issue of your chosen type: summary, description with business requirements and user stories, and links reflecting dependencies. Your team triages, comments, and transitions issues exactly as before; the agents follow your workflow.

## Troubleshooting

- **The Jira card shows "Coming soon".** Jira availability is rolling out per organization. Contact support to have it enabled for your workspace.
- **Agents are not picking up tickets.** Check the status map. Unmapped stages keep the corresponding agents paused by design.
- **The connection shows as expired.** Atlassian access tokens rotate; reconnect from the Jira card. Your project bindings and status maps are preserved.

## Next steps

- [From brief to tickets](/docs/your-first-brief-to-ticket-project)
- [GitHub](/docs/github) to connect the repository the tickets get built in

---
Canonical page: https://www.commercecopilot.ai/docs/jira