-
Bug
-
Resolution: Won't Fix
-
Low (View bug fix roadmap)
-
None
-
6.1.6
-
6.01
-
(This applies to the Scrum board's burndown chart.)
When someone logs work and makes a huge mistake with the remaining estimate - e.g., entering days instead of hours (due to the default time unit) -, the burndown chart's remaining estimates line will show a spike. When correcting the mistake by editing the work log entry and fixing the remaining estimate, the spike should be removed, but it is not. For an example, see the attached file "burndown.png" and for the culprit, see "logged hours.png".
These spikes can get so high that the burndown chart is no longer readable, see "burndown2.png".
- is related to
-
JSWSERVER-8439 As a product owner, I need to fix estimates which break Burndown and other reports
- Closed
[JSWSERVER-9862] Spikes in remaining estimate are not removed from Burndown Chart even when remaining estimate is corrected
| Minimum Version | New: 6.01 |
| Workflow | Original: JAC Bug Workflow v2 [ 2849845 ] | New: JAC Bug Workflow v3 [ 2936084 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2544755 ] | New: JAC Bug Workflow v2 [ 2849845 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1551325 ] | New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2544755 ] |
| Labels | New: affects-server |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 908634 ] | New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1551325 ] |
| Workflow | Original: GreenHopper Kanban Workflow 20141014 [ 746867 ] | New: JIRA Bug Workflow w Kanban v6 [ 908634 ] |
Hi Atlassian,
we decided to use Jira Agile on your Cloud a few weeks ago. Now we faced with exacly this bug and tried to resolve it removing bad entered times inside the issue. As it is not possible to fix this on Jira Agile - we must think if Jira fits best for us. We were strongly surprised that you decided to not fix this bug but it is a blocker for the customer on Jira Agile Cloud platform.
Because we entered a value which lead to peak of the chart is too high (months instead of minutes) the Burndown for the whole sprint is not usable anymore. We are not able to see where we are.
So please think again if this bug has no value as the applications behavior is not as required and customers have no workaround.
Best Regards,
Jan
| Workflow | Original: GreenHopper Kanban Workflow v2 [ 558730 ] | New: GreenHopper Kanban Workflow 20141014 [ 746867 ] |
@zchaudhary, @webcontrol, @simon.fox: I think resolved issues are no longer monitored as closely as active ones. Maybe it would be better if you created a new issue describing the problem and commented here with the new issue URL.