Version 2.13.0 · Released July 2, 2026 · Jira Cloud. Available now — no configuration required.

Every release date has three quiet enemies: dependencies, capacity, and scope creep. The app has measured the first two for months. Version 2.13.0 closes the loop on the third — scope creep is now visible, quantified, and fed straight into your probabilistic forecast.

What's new

Scope now moves both ways

Previously the burn-up scope line could only climb; when an issue left a release it vanished from the data, so de-scoping was invisible and impossible to audit. Now removals are captured durably — whether you drag a card out of scope in the app or change the Fix Version directly in Jira — and the scope line steps down to reflect them. Pull an item out and the line drops immediately to meet the projection and percentile lines.

See how fast scope is growing

Scope change is expressed as a rate, not a vague feeling: a percentage of change (for example, “100% growth”) and a per-day pace such as “+10% per day”. Creep becomes a number you can put in front of stakeholders.

The forecast adjusts to scope

Scope changes flow into the Monte Carlo simulation (and the scope-creep math ignores removed issues), so your P50 / P85 / P95 dates react as scope grows or shrinks — turning a scope-driven slip into a dated, attributable event you can respond to early.

What's in this release

Learn more

• The Three Productivity Killers of Release Planning — and How v2.13 Tames Scope Creep (divim.io)

• Managing Scope Creep with a MoSCoW Cut-Line: How It Works

Get started

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

Previous release: Version 2.11.0: Performance & Deeper Hierarchies.