Jira Version Report - Date Prediction Limitations

[Mike O'Connor]

The Jira Version report will not provide predicted completion dates until 10% of the estimated work has been completed according to the documentation: 

https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-version-report/#:~:text=10%25%20of%20the%20estimated%20work%20for%20the%20version%20will%20need%20to%20be%20complete%20before%20the%20predictions%20can%20be%20calculated.

Question: is the 10% based on the points, or issue volume?

Consider the following scenario:

• 9 issues in the backlog.
• Story 1 is 1 point, and all others are 3 points (25 total points)
• If I complete story 1, that represents 11% (1 / 9) of the backlog by issue volume, but only 4% (1 / 25) of the backlog by estimation (points).

It is not clear the documentation whether the report should be able to provide estimates.

[Walter Buggenhout · Accepted solution]

Hi @Mike O_Connor,

How the 10% is measured by the estimation statistic you configure in your board settings, as described in the article:

• The horizontal axis starts on the version's Start Date; or if no Start Date is specified, the date on which an issue was first added to the version. The graph shows the state your version was in at any given point in time, in terms of your total and completed Story Points (or other Estimation Statistic of your choice), so that you can see how the scope may have changed, and how you are progressing towards completion of the estimated work.

You define this in Board Settings > Estimation and it can be either Story Points, Issue Count or basically any numeric field of your choice:

Hope this helps! 

[Mike O'Connor]

@Walter Buggenhout  - Perfect, that is exactly what I was looking to confirm. Thanks very much.