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

Burndown doesn't adjust remaining time when closing a task

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Answered
    • Icon: Medium Medium (View bug fix roadmap)
    • None
    • None
    • None
    • None

    • GreenHopper (v6.1.3.1) JIRA (v5.0.2#725-sha1:5735107)

      The Board's Estimation/Time Tracking option is set to 'Remaining Estimate and Time Spent'

      1) Create a subtask of a story in the active sprint
      2) It's estimated time should be 10 hours
      3) Log 5 hours
      At this point the burndown should correctly log 5 hours spent and 5 remaining
      4) Resolve the issue (leave 'Remaining Estimate' set to Adjust automatically and don't log any additional time)
      The burndown chart will not remove the last 5 hours from 'Remaining Estimate' even though the JIRA issue correctly resets the remaining time to 0h

      The workaround seems to be to either log work when closing an issue, or manually set the remaining time to 0 by logging work before closing the issue. Once the issue is closed, it's a bit more work to fix the burndown chart (assuming you know which issues were improperly closed)

          Form Name

            [JSWSERVER-7704] Burndown doesn't adjust remaining time when closing a task

            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2850049 ] New: JAC Bug Workflow v3 [ 2936408 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2544886 ] New: JAC Bug Workflow v2 [ 2850049 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1551541 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2544886 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 909492 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1551541 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow 20141014 [ 746711 ] New: JIRA Bug Workflow w Kanban v6 [ 909492 ]
            mtokar.adm made changes -
            Workflow Original: GreenHopper Kanban Workflow v2 [ 494360 ] New: GreenHopper Kanban Workflow 20141014 [ 746711 ]
            Peter Obara made changes -
            Resolution New: Answered [ 9 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

            Bryan Young added a comment -

            That was the problem! Thanks for your help

            Bryan Young added a comment - That was the problem! Thanks for your help

            Shaun Clowes (Inactive) added a comment -

            I think you'll need to open a ticket with support to reproduce this issue.

            The most likely cause of this is when the issue history doesn't correctly contain an entry showing the remaining estimate moving from 5h to 0h (you can check for this in the 'All' tab of the Activity section of the view issuepage). JIRA does not normally 'reset the remaining time to 0h' when an issue is resolved but many users add a post function to the workflow to do so, the most common cause of this problem is when the post function is incorrectly configured to occur after issue history has been written.

            Thanks,
            Shaun

            Shaun Clowes (Inactive) added a comment - I think you'll need to open a ticket with support to reproduce this issue. The most likely cause of this is when the issue history doesn't correctly contain an entry showing the remaining estimate moving from 5h to 0h (you can check for this in the 'All' tab of the Activity section of the view issuepage). JIRA does not normally 'reset the remaining time to 0h' when an issue is resolved but many users add a post function to the workflow to do so, the most common cause of this problem is when the post function is incorrectly configured to occur after issue history has been written. Thanks, Shaun
            Bryan Young made changes -
            Description Original: 1) Create a subtask of a story in the active sprint
            2) It's estimated time should be 10 hours
            3) Log 5 hours
            At this point the burndown should correctly log 5 hours spent and 5 remaining
            4) Resolve the issue (leave 'Remaining Estimate' set to Adjust automatically and don't log any additional time)
            The burndown chart will not remove the last 5 hours from 'Remaining Estimate' even though the JIRA issue correctly resets the remaining time to 0h

            The workaround seems to be to either log work when closing an issue, or manually set the remaining time to 0 by logging work before closing the issue. Once the issue is closed, it's a bit more work to fix the burndown chart (assuming you know which issues were improperly closed)             		New: The Board's Estimation/Time Tracking option is set to 'Remaining Estimate and Time Spent'

            1) Create a subtask of a story in the active sprint
            2) It's estimated time should be 10 hours
            3) Log 5 hours
            At this point the burndown should correctly log 5 hours spent and 5 remaining
            4) Resolve the issue (leave 'Remaining Estimate' set to Adjust automatically and don't log any additional time)
            The burndown chart will not remove the last 5 hours from 'Remaining Estimate' even though the JIRA issue correctly resets the remaining time to 0h

            The workaround seems to be to either log work when closing an issue, or manually set the remaining time to 0 by logging work before closing the issue. Once the issue is closed, it's a bit more work to fix the burndown chart (assuming you know which issues were improperly closed)

              Unassigned Unassigned
              a70f1e6de530 Bryan Young
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: