# Assign a Jira ticket and get back a verified pull request

> Early access: assign a Jira ticket to SHIP's agent team. Get back a pull request that passed your CI, a code review and a test on a live preview.

Early access, for engineering teams.

SHIP's agent team plans, builds, reviews and tests the change a Jira ticket asks for. You get a pull request that passed your CI.

- **For:** Engineering teams that plan their work in Jira and already pay for a coding agent.
- **Instead of:** A coding agent that opens a draft and leaves every check to you.
- **Runs today:** Linear and GitHub Issues work today. Assign the issue in Linear, or comment @SHIP on a GitHub issue. From a terminal, ship delegate plan builds from a spec you wrote.

## Move a ticket to a pull request in three steps

1. **Connect Jira and GitHub.** Authorize your Jira site and install the SHIP GitHub App on your repositories. A project pins one Jira project and one repository.
2. **Write the acceptance criteria.** Write what done looks like as a checklist on the ticket. The Tester checks the change against it on a preview.
3. **Give the ticket to SHIP.** Set SHIP as the assignee. The plan, the review verdict and the test result appear on the ticket as the mission advances.

## Get more than a draft pull request

- **Plan before any code exists.** The Planner reads the ticket and the repository and writes a plan. A checkpoint can hold the mission until you approve it.
- **Gate every change on your CI.** A failed check goes back to the Builder with its logs. The pull request reaches you only after your CI passes.
- **Review with a second agent.** A Reviewer that did not write the code reads the diff against the plan. It lists the fixes it requires and the ones it only suggests.
- **Test the change on a preview.** The Tester runs the acceptance criteria against a live preview and attaches a browser trace and screenshots as proof.
- **Pick the harness and model per role.** Run each role on claude-code, codex or an open-weight model, on your own provider keys.

## Check the loop on 260 missions

In the SWE-in-a-team study, 260 missions went through the loop that early access brings to Jira. The loop sent 46 runs back and corrected 40 of them without a person.

- [Read the SWE-in-a-team study](https://letsship.ai/blog/swe-in-a-team)

## Compare SHIP with the agents Jira already starts

- **SHIP:** In early access: Takes the ticket through a Planner, your CI, a Reviewer and a Tester before the pull request reaches you.
- **SHIP:** In early access: Posts the plan, the review verdict and the proof from the test on the ticket.
- **SHIP:** Generally available: Runs each role on the harness and model you choose, on your own provider keys. ([Schema](https://letsship.ai/docs/configuration/schema))
- **Claude Agent for Jira:** Takes coding work from a Jira work item that you assign to it or mention. It typically opens a draft pull request from a service account. ([Set up Claude Agent for Jira](https://support.atlassian.com/jira-software-cloud/docs/set-up-claude-agent-for-jira/))
- **GitHub Copilot:** Starts its cloud agent when you assign a Jira work item to it or mention it in a comment. The activity streams into a chat panel in Jira. ([Integrate Copilot cloud agent with Jira](https://docs.github.com/en/copilot/how-tos/copilot-integrations/integrate-cloud-agent-with-jira))
- **Cursor:** Works on Jira work items that you assign to it or mention, and links the pull request in its completion update when it opens one. It needs a Teams or Enterprise plan. ([Cursor Jira integration](https://cursor.com/docs/integrations/jira))

Last reviewed October 15, 2026, from each product's own pages.

## Frequently asked questions

### Is the Jira integration available today?

Not yet. Jira is in early access, and SHIP works with Linear and GitHub Issues today. A team on Jira can start a mission from a terminal with ship delegate plan and a spec file. [Ways of working](https://letsship.ai/docs/getting-started/ways-of-working)

### When is Claude Agent for Jira, GitHub Copilot or Cursor the better fit?

They fit a team that wants an agent to start a pull request from Jira and then reviews and tests it by hand. Cursor needs a Teams or Enterprise plan for this. SHIP fits a team that wants the plan, CI, review and a preview test done before the pull request reaches anyone.

### Which coding agents does SHIP run?

SHIP runs claude-code, codex, pi, kilo-code and open-code. You set the harness and the model for each role in ship.yml, on your own provider keys. [Schema](https://letsship.ai/docs/configuration/schema)

### What happens when I join the early-access list?

You answer four questions about your team and the coding agent you use. SHIP emails you when the Jira integration opens to your team.

## Join early access for Jira

Join the list, and get your first Jira ticket back as a verified pull request.

Source: https://letsship.ai/platform/jira