Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-1726

As a user, I would like the time estimates of new issues added during the middle of a sprint to be reflected as a spike in the burndown chart.

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 6.0
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Sometimes during the course of a sprint, there are new tasks that need to be added that were not known during sprint planning. When we create new issues to represent these tasks, we assign a time estimate (under the "original time estimate" field). The problem is that the chart board then reflects it as if this estimate was known at the beginning of the sprint. What we would like to see if a spike in the chart. The time estimate should be applied based on the date that the issue was created.

      This is important in having a true representation of the burndown. It's valuable to see how the burndown is affected by new tasks arising mid-sprint.

      The only known workaround for us is to enter an original estimate of "1 minute", and then set the appropriate "remaining estimate" as the actual time estimate. But this isn't intuitive...

            [JSWSERVER-1726] As a user, I would like the time estimates of new issues added during the middle of a sprint to be reflected as a spike in the burndown chart.

            Shaun Clowes (Inactive) added a comment -

            The burndown chart in the new boards handles this situation correctly.

            Thanks,
            Shaun

            Shaun Clowes (Inactive) added a comment - The burndown chart in the new boards handles this situation correctly. Thanks, Shaun

            Deleted Account (Inactive) added a comment -

            @Kevin i am really missing this as well. I was wondering if that was a bug when i just added a new issue to a ongoing sprint. What i saw was that Green / Red curve at x=0 was equal to the ammount of work left including the issue i just added.

            When i read the documentation here : http://confluence.atlassian.com/display/GH/How+Hour+Burndown+Charts+Relate+to+Time+Tracking+in+JIRA it should have worked as i was expecting it and that is i should see the Red curve remain as it was before adding the issue and the Green curve should increase as shown in the documentation.

            I would say this is a bug. If it's not taken as a bug then documentation should be corrected to reflect the way it works.

            Anyone care to comment ?

            Deleted Account (Inactive) added a comment - @Kevin i am really missing this as well. I was wondering if that was a bug when i just added a new issue to a ongoing sprint. What i saw was that Green / Red curve at x=0 was equal to the ammount of work left including the issue i just added. When i read the documentation here : http://confluence.atlassian.com/display/GH/How+Hour+Burndown+Charts+Relate+to+Time+Tracking+in+JIRA it should have worked as i was expecting it and that is i should see the Red curve remain as it was before adding the issue and the Green curve should increase as shown in the documentation. I would say this is a bug. If it's not taken as a bug then documentation should be corrected to reflect the way it works. Anyone care to comment ?

              Unassigned Unassigned
              989d1b8add2f Kevin MacClay
              Votes:
              5 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: