Version Report Changes

[Pradeep Mathew]

i planned a release with x amount of stories and in the version report it was predicting the optimistic and pessimistic dates based on the velocity. But later in between the release i updated the release date for that release and reduced the scope of the release drastically. Still the Predicted dates are not getting changed. Please advice on what can be done to reflect the changes.

[Troy Spetz]

We use JIRA Server 7.10 version.

Since last April, I've been manually tracking (in a spreadsheet) the 3 dates generated by the Version Report for the current release we are developing.

Since that time, I have not been able to make any sense of how it calculates the Optimistic, Predicted and Pessimistic dates. The end result was that the dates were next-to-useless in helping me to determine when the release would be done.

Instead, I use the Release Burndown report, as this report is based on (at least) 3 previous sprints completed velocity then applies this average velocity to the work remaining. It appears to be more accurate in both historical reporting, as well as estimating the future completion date (in terms of sprints remaining).