Platform
Forecasts you can hand to a stakeholder and defend afterwards.
Delivery forecasting fails in three specific, measurable ways: scope grows and nobody counts it, dormant work gets projected as if it were active, and throughput is estimated from a good fortnight. Pacia handles all three explicitly, and shows you the inputs so you can judge how much to trust the answer.
- Scope now
- 84 issues · 31 added since start
- Completed
- 52 of 84
- Throughput, last 6 weeks
- 6.2 issues/week
- Forecast
- mid-October · low confidence
- Started
- First child issue, 14 April
Low confidence is shown, not hidden. A weak forecast should look weak.
What the delivery views cover
Sprint delivery
Planned, added mid-sprint, delivered and carried out, per sprint. Sprint membership changes are read from the Jira changelog, so injected work is visible as injected work.
Sprint planning
A forward view of the sprint being assembled, against what this team has historically actually completed rather than what it hoped to.
Epic health
Every epic with its progress, scope growth, dormancy state and forecast. The fastest way to find the four epics nobody has touched since spring.
Epic detail
One epic in full — child issues, throughput, timeline, and the calculation behind its forecast.
Epic comparison
Several epics side by side on identical measures, for when the question is what to cut rather than what to expect.
Work item timeline
A single issue’s journey through every stage, including how long it waited at each one.
What a forecast gets wrong before you fix it
Each of these produced an obviously absurd number on a real Jira site before the rule existed. They are the difference between a forecast you can show a stakeholder and one that quietly discredits the page it appears on.
The three rules that stop a forecast embarrassing you
- Epic raised 2 MarchClock starts at first child issue, 14 April
Epics are raised weeks before anyone works on them. Dating from creation makes every team look slow.
- Grew 1 → 84 issues = 8,300% of plan31 of 84 added since start = 37% of total scope
Measured against the initial batch, ordinary scope growth produced a figure of 16,700% on real data.
- Untouched 94 days, forecast: March 2033Marked dormant, no forecast issued
Nobody closes a finished epic in Jira. Projecting one produces a date that discredits every other forecast on the page.
The rules behind every forecast
The three above, plus two that decide whether the number is current and whether it fits your Jira site rather than someone else’s.
An epic starts at its first child issue
Not the day it was raised. Epics are routinely created weeks or months before anyone works on them, and dating them from creation makes every team look slow.
Scope growth is measured against total scope
Not against the initial batch. Epics routinely start life with a single issue, and measuring growth as a percentage of the plan produced a scope-growth figure of 16,700% on real data.
Dormant epics get no forecast at all
An open epic untouched for 90 days or more is marked dormant and excluded. Nobody closes a finished epic in Jira, and projecting one produced completion dates in 2033.
Nothing tenant-specific is hardcoded
Epics are identified by Jira’s own hierarchy level rather than by an issue type named "Epic", because every Jira site has its own vocabulary and a guess is actively wrong.
The delivery cache is not a live Jira call
Sprint and epic pages read from a synced cache filled hourly and by an explicit refresh button, and they say when they were last read. A full sprint and epic pass costs roughly 1.6% of one hour’s Jira API quota.
Common questions
Do we need story points?
No. Forecasts work from issue counts and observed throughput. If your site has a populated story-points field it can be used, but it must be identified explicitly — a typical Jira site has around seven point-ish custom fields and only one is actually filled in.
Does Pacia write anything back to Jira?
No. The Jira integration is read-only. Nothing on your board changes because you connected it.
Which Jira products are supported?
Jira Cloud, using an API token. Sprints, epics, boards, changelogs, issue links and resolutions are read; the configuration mapping step confirms how your site expresses defects, statuses and hierarchy before any rule uses them.