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

Edit issue and set 'Remaining Estimate' to zero - does not accurately reflect in burndown.

      I selected a task to edit, and I changed the remaining estimate field to zero. This did not update the chart board. The burndown still included the hours I had cleared out. When I ran the 'Chart Data' report, I could see the hours will still showing against the task.

            [JSWSERVER-1957] Edit issue and set 'Remaining Estimate' to zero - does not accurately reflect in burndown.

            Tadhg Tadhg added a comment - - edited

            The attached PDF gives the steps that will reproduce the error.

            I have also raised another issue JSP-51222 which should be linked to this, once JSP-51222 has been ratified.

            Tadhg Tadhg added a comment - - edited The attached PDF gives the steps that will reproduce the error. I have also raised another issue JSP-51222 which should be linked to this, once JSP-51222 has been ratified.

            for relating problems and details also see http://forums.atlassian.com/thread.jspa?messageID=257329830

            Tilfried Weissenberger added a comment - for relating problems and details also see http://forums.atlassian.com/thread.jspa?messageID=257329830

            This is a major confusion for us. When the Burndown does not match the remaining estimates in the tickets - then this is very bad. Also our workflows will set remaining estimates to 0, when issues are rejected for example.

            Tadhg Tadhg added a comment - This is a major confusion for us. When the Burndown does not match the remaining estimates in the tickets - then this is very bad. Also our workflows will set remaining estimates to 0, when issues are rejected for example.

              Unassigned Unassigned
              7ecea2741590 Soleil Hefferen
              Affected customers:
              2 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: