Ace Foundry

Capacity Trail for Jira

How many hours the team has, how much is already on them, and the gap.

Every capacity figure it publishes carries a sentence saying what it counted: the people, the working days, who is being assumed to take no leave, how many issues had no estimate, and how much work is sitting unassigned. That sentence is there when nothing was excluded too.

The number nobody re-adds

A capacity figure is produced once and committed against. Nobody derives it again. So the ways it can be quietly wrong matter more than the ways it can be obviously wrong, and nearly all of them make the team look like it has more room than it has: an unestimated issue counted as no work, unassigned sprint work left out of the sum, somebody on leave counted as fully available, a query too big to read completely.

What it does differently

It refuses rather than guesses. If the read cannot finish, no figure is published. A partly read query hides work that is already assigned.

It names its assumptions. Anybody counted as fully available is listed by name, under those words.

You decide what counts as the work. Everything your query returns, or only issues with a due date inside the period. There is no default, because a capacity figure means two different things depending on which you pick, and the report says which one it used.

Spare time is shown as a ceiling when it is one. An issue with no estimate counts as no work, so if anything in scope is unestimated the figure reads "up to", not a flat number. A report that says exactly how much room a team has, when part of the work has never been sized, is the thing this app exists to replace.

It needs no second product. It reads the estimates already in your Jira. There is no timesheet subscription behind it.

It reads as you. Your figures are bounded by your own Jira permissions, and the report says so.

Support

Email hello@acefoundry.io and a person answers. If a capacity figure was ever wrong in a way the coverage sentence did not flag, say so and it goes to the top of the queue, because that is the exact failure this product exists to prevent.

Runs entirely inside Atlassian

Built on Forge, read-only, no external egress, and it stores nothing about any person. See the privacy policy.