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

The Burndown Chart does not consider JIRA post function when calculating Remaining Estimate

    XMLWordPrintable

Details

    Description

      NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.

      Steps to replicate:

      1. The issue's Original Estimate is set to 8h
      2. The user logs in a 4h work and closes the issue
      3. The Remaining Estimate will be reduced to 4h
      4. Post-function from the workflow sets the Remaining Estimate to 0h
      5. Greenhopper does not understand that the Remaining Estimate had been decreased first by 4h and then by 4h again.

      If the post-function of Update Issue Field is not used, the issue does not occur. Considering the post-function ships with the out-of-the-box, JIRA, it should take into consideration of setting the Remaining Estimate to 0.

      Attachments

        1. post_functions.png
          39 kB
          Fabian Meier
        2. sprint_report_01.png
          44 kB
          Fabian Meier
        3. sprint_report_01b.png
          55 kB
          Fabian Meier
        4. sprint_report_01c.png
          55 kB
          Fabian Meier
        5. sprint_report_01d.png
          44 kB
          Fabian Meier
        6. sprint_report_01e.png
          50 kB
          Fabian Meier
        7. sprint_report_02.png
          15 kB
          Fabian Meier
        8. sprint_report_02b.png
          23 kB
          Fabian Meier
        9. sprint_report_02c.png
          69 kB
          Fabian Meier
        10. useless_burndown.png
          14 kB
          Fabian Meier

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JSWSERVER-9079 Remaining time estimates not updating on Burndown chart

          • Low - Low priority issues
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-31929 Update Issue Field Post-Function using Time Spent does not work

          • Medium - Medium priority issues
          • Gathering Impact

          Suggestion - JSWSERVER-8340 Burndown report includes time remaining from Resolved and Closed issues.

          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JSWSERVER-8191 Total time remaining is incorrect if user edits the work log and sets Remaining Estimate manually

          • High - High priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-65078 Update issue field post function gets saved twice in issue history if it is placed first in the list of post functions

          • Medium - Medium priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JSWCLOUD-6788 The Burndown Chart does not consider JIRA post function when calculating Remaining Estimate

          • Medium - Medium priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-66261 Ofbiz and business layer piercing: manipulating directly the ofbiz GenericValue on time-tracking.

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JSWSERVER-9316 Rapid Boards do not report burndown as expected with edits to work log

          • Low - Low priority issues
          • Closed
          mentioned in

          Page Loading...

          Activity

            People

              Unassigned Unassigned
              adanial Ahmad Danial (Inactive)
              Votes:
              55 Vote for this issue
              Watchers:
              42 Start watching this issue

              Dates

                Created:
                Updated: