Release Management, Roadmaps, Portfolio PPM & Timeline for Jira brings your entire product portfolio and its release roadmaps into one place in Jira. It groups work into products and releases, lays every product’s releases on a single portfolio timeline, projects realistic completion dates from each team’s actual throughput, and shows scope, capacity, and dependencies together. This guide walks through the app screen by screen.
Getting started
After installing the app from the Atlassian Marketplace, open it from Jira’s left sidebar under Apps → Release Planning. The app is a Runs-on-Atlassian (Forge) app, so your data never leaves your Atlassian cloud. Everything is organised around two ideas: a Product (a stream of work, mapped to Jira projects and a board) and the Releases within it (your Fix Versions). Multiple products roll up into one portfolio view.
1. Set up a product
Go to the Settings tab and create a product. Give it a name, then connect the Jira project(s) and the board whose throughput should drive the forecast. You can manage several products from the same place — each gets its own roadmap, releases, and capacity, and together they form your portfolio.
2. Plan the scope
The Product Planning tab is where you decide what goes into each release. Drag work items between the backlog and your releases, filter by team or label, and watch the totals update. This is the source of truth for what the forecast is predicting against.
3. View the roadmap
The Product Roadmap tab lays your releases out on a portfolio timeline so stakeholders can see what ships when across every product. Bars reflect each release’s planned window; the roadmap stays in sync with the scope you set in Product Planning.
4. Forecast the release
The Release Planning tab is the heart of the app. It runs a Monte‑Carlo simulation on your team’s real throughput to forecast when the selected scope will actually be done — as a probability, not a single optimistic date.
- Probability of completion curve — the S‑curve shows the likelihood of finishing the scope by any given date, blending scope, work done, and projection.
- Releases — select a release to forecast just its scope, or view the entire product backlog. Each release shows its item count and progress.
- Confidence bands — Risky (P50, 50% chance), Likely (P85), and Very likely (P95) give you a date you can actually defend to stakeholders.
- Scope (IN / OUT) — drag work items between lanes to add or remove them from the release and watch the forecast update live.
Tip: if you see a “sparse data” or throughput warning, the team has fewer than four weeks of completed work recorded. Forecasts get sharper as more throughput accumulates.
5. Plan capacity
The Capacity Management tab shows how much the team can realistically take on across the plan, so releases are sized against real availability rather than wishful thinking. Turn on capacity awareness in Release Planning to factor it into the forecast.
6. Manage dependencies
The Dependency Management tab maps what blocks what across the release. Spot critical paths and cross‑team blockers before they put the date at risk, and enable dependency awareness so the forecast accounts for them.
7. Share the executive summary
The Summary tab rolls everything up into a stakeholder‑ready dashboard: release status, forecast dates, work remaining, and throughput at a glance — ideal for steering meetings and portfolio status updates.
Need help?
Questions or feature requests? Reach the Divim team through our Help Center, or view the listing on the Atlassian Marketplace.