Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
Description
Problem
When visualizing the Release Burndown Chart agile report, you cannot easily find what action determined the baseline date of the initial sprint for the release. This baseline is what dictates which issues will be under "Original estimate at the start of version" and also on the "Before Initial sprint" section at the end of this report.
Suggested Solution
Add another field on this report (above Planned start date, for example) to show the baseline
Why This Is Important
At times users may not understand why some issues show "Before Initial Sprint" or why there are a lot of tickets undder "Original estimate at the start of version".
Since the baseline of the initial sprint is a critical and it cannot be changed, knowing what caused an unexpected result can prevent issues from reoccurring as well as giving more confidence on the results of the report.
Workaround
There is no workaround. From Some Completed Sprints are not visible in the "Release Burndown"; report there's this explanation but determining the actual baseline is a very complex task.
Basically, when a release is established, the first issue created in the first sprint associated with the version will establish the baseline of the initial sprint. This cannot be changed or modified. The moment an issue from a Sprint is added to a version, that moment decides the starting point for the report. All the issues from earlier Sprints that get added to the version, will be added to the Before initial sprint section.