Common questions about Release Management, Roadmaps, Portfolio PPM & Timeline — Divim’s product-portfolio and release-forecasting app for Jira Cloud. Plan every product’s releases on one portfolio timeline, then forecast a date you can commit to from your teams’ real capacity. For a step-by-step guide, see our Release & PI Planning in Jira resource hub.
What is Release Management, Roadmaps, Portfolio PPM & Timeline for Jira?
It’s a Jira Cloud app for managing your product portfolio and release roadmaps in one place. Every product’s releases sit on a single portfolio timeline, each ranked by delivery confidence, so leaders can see the whole portfolio at a glance. Under each release, instead of a single optimistic target date typed in by a human, it gives three confidence-based dates — for example, “50% chance by May 10, 85% by May 24, 95% by Jun 7” — calculated by Monte Carlo simulation over your teams’ real historical throughput. It also blends in real team capacity (PTO, holidays, working days), maps dependencies, and lets you prioritize scope with frameworks like WSJF, RICE, and MoSCoW — all natively inside Jira and rolled up across the portfolio.
How does the probabilistic release-date forecast work?
The app runs a Monte Carlo simulation over your team’s actual completed-work history (throughput) from Jira. Rather than promising one date, it returns a range of outcomes with confidence levels — P50, P85, and P95 — shown as color-coded confidence bands (Risky, Likely, Very Likely) on the Release Planning board. You can toggle capacity awareness and dependency awareness to factor those into the projection. If your throughput history is too sparse, the app shows a warning and lowers confidence, so you know when to trust the numbers and when to feed it more completed work.
How is this different from Jira’s built-in roadmaps?
Roadmap and timeline tools draw the dates you type into them — they look precise but reflect intent, not evidence. Release Management, Roadmaps & Portfolio calculates the dates from your teams’ real flow data and rolls them up into one portfolio timeline, so the whole portfolio’s forecast updates as work actually progresses. In short: a roadmap describes what you hope to ship; this app tells you the probability you’ll actually hit it across every product, and lets you negotiate scope-versus-date trade-offs with data instead of opinions. It complements portfolio tools like Jira Align rather than replacing them.
Does it support multiple teams and multiple boards?
Yes. A “product” groups one or more Jira boards that ship together so forecasts and reporting roll up across them, and multiple products roll up into the portfolio. In the Advanced edition, you can assign multiple teams to a product and the forecast uses weighted capacity aggregation — blending the combined throughput of every team contributing to a release. You can run the forecast in throughput-only mode (pure flow data) or capacity-blended mode (throughput weighted by who is actually available).
How does capacity planning work (PTO, holidays, working days)?
Capacity is configured under Capacity Management → Teams, where you create teams, add members, and set each member’s non-working days and availability. You can choose which days of the week count toward schedule calculations and import public holidays in bulk via CSV. A PTO picker tied to real Jira users means the forecast moves automatically when the right people are out. The Capacity Report also flags overcommitment — when committed scope exceeds what a team can likely finish at 85% confidence.
Can I prioritize what goes into a release?
Yes — and prioritization is scoped to the selected Fix Version, so you’re ranking the work in this release, not your whole backlog. On the Release Planning board you can switch between several prioritization views: Scope (In/Out), MoSCoW, Eisenhower, Value × Effort, WSJF, and RICE. The MoSCoW lane view includes a draggable cut-line and a one-click action to move items that no longer fit, so scope decisions stay visible and defensible.
Does it handle dependencies between issues?
Yes. The Dependency Management tab has two views. The Dependency Map shows linked issues as an interactive graph where you can create or remove links, drag issues onto the canvas, and open issues directly. The Critical Path view highlights the longest chain of dependent issues — the chain that determines your minimum delivery time. Dependencies created on the map flow into the critical path automatically and can be factored into the forecast.
Where is my data stored — is it secure?
Your data never leaves Atlassian. Release Management, Roadmaps & Portfolio is built entirely on Atlassian Forge (Forge SQL + KVS), so your scope, forecasts, capacity models, and pending changes are stored inside your own Atlassian tenant. The app makes no outbound calls to Divim or any third party — no analytics SDK, no external error reporter, no vendor-side copy of your roadmap. It inherits Atlassian’s SOC 2 / ISO 27001 posture and tenant isolation, data follows your Jira Cloud site’s data-residency region automatically, and the app carries both the Runs on Atlassian and Cloud Fortified designations. Full details are in the Divim Trust Center.
What do I need to install it, and how do I get started?
You need a Jira Cloud site. Install the app from the Atlassian Marketplace, then go to Settings → Products and use the Create a new product wizard: name the product, pick one or more Jira boards as sources, choose your working days, and map Jira priorities into Must/Should/Could/Won’t buckets. Point it at a Fix Version and you’ll see your first probabilistic forecast within minutes, backed by your team’s real flow data.
How much does it cost — is there a free trial?
Yes, there’s a free trial through the Atlassian Marketplace, and the app is free for small teams under Atlassian’s standard small-team pricing. Beyond that it’s a paid Marketplace app billed through your Atlassian account, with pricing that scales by user tier. Because pricing can change, check the live figures on the Atlassian Marketplace listing.
What’s the difference between the Standard and Advanced editions?
Standard includes the core engine: probabilistic release-date forecasting, capacity-aware planning, scope-risk and dependency analysis, backlog prioritization, and release burnup/completion charts. Advanced adds portfolio-scale capabilities on top: multi-board releases, multiple products tracked in one interface, the Portfolio view (every active release ranked by confidence), the executive Product Roadmap timeline, multi-team assignment, and overcommitment warnings.
How do I get support?
You can reach the team through the Divim support portal linked on the Marketplace listing, or email support@divim.io. The published User Guide, Data Security & Privacy Statement, and Security Policy (including how to report a vulnerability) are all available in the documentation site. Security questions are acknowledged within five business days.
Release Management, Roadmaps, Portfolio PPM & Timeline for Jira is built by Divim, an Atlassian Marketplace Partner since 2018. View the app on the Atlassian Marketplace.