Shipped

Jira says what you planned to ship.
Git knows what you shipped.

Shipped reads your semver tags and commits, finds the tickets in each component version, flags drift between Jira and reality, and lets QA mark each ticket tested. One CI step, any git host, and your data never leaves Atlassian.

Get it on the Atlassian MarketplaceRead the setup guide

Release scope from git

Every ticket in api 1.5.0, web 3.2.1 and worker 0.9.0, found automatically from the commits between tags. No Fix Version guesswork.

QA sign-off in one matrix

Mark tickets Passed, Failed or Blocked across components, in bulk. Know exactly what's left before you release.

Catch drift early

Planned but not shipped, shipped but not planned, code with no ticket, reverts, and tickets that aren't Done, per release.

Any git host, any CI

GitHub, GitLab, Bitbucket, Azure DevOps, Jenkins or plain git. No tokens to store: your CI pushes a signed summary on each tag.

Runs on Atlassian

Built on Atlassian Forge with no external servers. Data stays in Atlassian's cloud, in your site's region.

Searchable in Jira

"Shipped in" on every issue, plus JQL: shippedTest = "failed", shippedIn = "api 1.5.0".

How it works

  1. Install Shipped from the Atlassian Marketplace and open Apps → Shipped.
  2. Copy one step into your CI. On every tag push it sends the commit messages since the previous tag.
  3. Group component versions into a release and let QA work through the matrix.

Pricing

Free for Jira sites with up to 10 users. Every site gets a 30-day free trial. See the Marketplace listing for current prices.