Version 3.0.0 · Released July 15, 2026 · Jira Cloud. Available now — no configuration required.

Atlassian's Product Collection is built on a simple idea: bring customer insights, prioritization, and delivery into one place so teams can build with confidence. Feedback captures the signal. Jira Product Discovery turns it into prioritized ideas and living roadmaps. Jira carries the work.

Version 3.0.0 answers the question that sits at the end of that chain — when will it actually ship, and how sure are we? This is our largest release to date: a release becomes a commitment you manage rather than a date you hope for, the portfolio becomes a triage queue instead of a status meeting, and — for the first time — release readiness publishes straight into Confluence, without your Jira data ever leaving Atlassian.

Where this fits in the Atlassian Product Collection

The Collection's third pillar is bridge strategy and execution — keep product decisions connected to Jira so context flows into engineering, progress stays visible, and stakeholders know when work ships. Version 3.0.0 is our contribution to exactly that pillar:

What's new

Manage to a commitment, not a forecast

A release now carries a first-class commitment: a target date, a confidence threshold, and a scope baseline. Lock the baseline and any drift from it is flagged as creep against what you actually committed to — not against a moving average. When the release lands, outcome fields capture what really happened and feed a post-release calibration retrospective, so your forecasts get measurably better at being right. The language across the app follows: what you commit to is a Commitment date, and it always travels with its confidence.

Why the date moved, in days

When a committed date moves, 3.0.0 tells you why — and puts a number on it. The drift-attribution engine decomposes every movement into its causes and quantifies each one in days: scope grew by 33 issues, that cost you 8.3 days; completion ran ahead of pace, that gave you 4.5 days back. Net +5. It also names the residual it cannot attribute, rather than quietly burying it. A drift narrative on the Summary dashboard turns that decomposition into a sentence you can paste into a status update, and forecast history snapshots persist the whole trail so the story survives past this week.

Systems, not oversight

Watching twenty releases is not a job for a human refresh key. Define a threshold watch once — per release or per product — and the app watches for you, raising an alert only when confidence crosses your line. The release health view shows exceptions only: the releases that need you, and nothing else.

Release Readiness, published to Confluence

The capability we listed as "coming next" is here. Release Management now publishes Release Readiness reports directly into Confluence — a weekly, auto-generated page so executives see the trend without opening the app. Configure a target space and parent page per product (the app verifies write access before you save, and links you to the space if it doesn't have it), and route pages to the right audience with per-page view restrictions.

Critically, this is on-platform. Publishing to Confluence uses Atlassian's own APIs from inside Forge — the app added Confluence read and write scopes in this build and no egress. Release Management, Roadmaps & Product Portfolio remains Runs on Atlassian: your Jira and Confluence data never leaves Atlassian's boundary to make this work.

The portfolio, as a roadmap and a queue

The Portfolio Roadmap puts every active release across every product on one timeline, grouped the way you think — by product, team, quarter, status, or fix-version stream — with swimlanes and keyboard-accessible ordering. Click a release and you land in its Forecast view, in context. Objectives-based prioritization ties releases to what they're for, and the whole portfolio exports to a shareable CSV for the stakeholders who will ask for a spreadsheet no matter what you build.

Prioritization that knows what it's prioritizing

Prioritization is now explicitly scoped: you rank within a release backlog or a product backlog, and the app stops pretending those are the same thing. MoSCoW, Eisenhower and Value×Effort no longer collapse a whole product backlog into "Won't have" or "Eliminate"; quadrant boards support drag-to-rank within a quadrant; and product-backlog rank changes flow through the same "Save N changes" queue as everything else.

Notifications and teams

Release changes — dates, scope, priorities, and releases going out — can now notify the people who care. Build notification groups from Jira users and Jira user groups, and tune what each group hears. Products can also carry multiple teams, so a product spanning several delivery teams models correctly.

Enterprise Certified readiness

This release carries the security-hardening and accessibility & privacy work for Atlassian's Enterprise Certified trust program, which replaces Cloud Fortified from Q3 CY2026. That work is landed; certification itself follows Atlassian's rollout.

What's in this release

Learn more

• Atlassian Product Collection — build products with confidence

• Portfolio Confidence Reporting for Executives: How It Works

• Choosing a Commitment Confidence Level: P50, P85 & P95

• Keeping a committed release date honest: scope, dependencies, and capacity

Get started

Try it on the Atlassian Marketplace · Learn more on divim.io · User Guide · Book a 30-minute demo

Previous release: Version 2.13.0: Scope Creep Awareness.