Step 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.
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.
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.
Answer 4 questions. SHIP emails you when it opens to you.
Step 1
Authorize your Jira site and install the SHIP GitHub App on your repositories. A project pins one Jira project and one repository.
Step 2
Write what done looks like as a checklist on the ticket. The Tester checks the change against it on a preview.
Step 3
Set SHIP as the assignee. The plan, the review verdict and the test result appear on the ticket as the mission advances.
The Planner reads the ticket and the repository and writes a plan. A checkpoint can hold the mission until you approve it.
A failed check goes back to the Builder with its logs. The pull request reaches you only after your CI passes.
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.
The Tester runs the acceptance criteria against a live preview and attaches a browser trace and screenshots as proof.
Run each role on claude-code, codex or an open-weight model, on your own provider keys.
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.
| Claude Agent for Jira |
|
|---|---|
| GitHub Copilot |
|
| Cursor |
|
| SHIP | In early access
|
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.
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.
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.
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 the list, and get your first Jira ticket back as a verified pull request.
Answer 4 questions. SHIP emails you when it opens to you.