Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-6788

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

XMLWordPrintable

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

      To replicate

      Set up the environment as follows:

      1. Should be in a classic project (sprint-enabled) 
      2. Workflow can be simple: Todo → In Progress → Done. (Best to edit a new workflow then activate it)
      3. Whilst creating the "In Progress" → "Done" transition in this workflow, assign a screen to it. (The screen can be pre-existing).
        1. Modify this screen: add the "Log Work" field.
      4. In this "In Progress" → "Done" transition, add a new post-function: "Update Issue Field" - setting "Remaining Estimate" to 0. Publish the workflow with these changes.
      • (Current incorrect behaviour: If the post-function is the first in the list, then "Remaining Values" won't be updated and "Time Spent" will.)
      • (Current incorrect behaviour: If the post-function is the last in the list, then "Time Spent" won't be updated and "Remaining Values" will.)

      Then, perform the following actions:

      1. Add a new issue to the sprint, of an issue type that the screen is assigned to.
      2. Set the Original Estimate of this issue to 8h
      3. On the board, drop this issue into the Done column following the workflow, the screen should appear. In the screen modal:
        1. Log in 4h work into Time Spent
        2. "Adjust automatically" should be checked for Remaining Estimate
      4. On transition completion, the post-function from the workflow should then automatically set the Remaining Estimate to 0h
      • 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.

        1. image-2021-01-07-14-22-14-664.png
          image-2021-01-07-14-22-14-664.png
          199 kB
        2. image-2021-01-08-10-44-19-580.png
          image-2021-01-08-10-44-19-580.png
          393 kB
        3. image-2021-01-08-10-46-52-994.png
          image-2021-01-08-10-46-52-994.png
          312 kB
        4. image-2021-01-08-10-48-51-254.png
          image-2021-01-08-10-48-51-254.png
          244 kB
        5. image-2021-01-08-10-51-17-918.png
          image-2021-01-08-10-51-17-918.png
          303 kB
        6. pf1.png
          pf1.png
          34 kB
        7. pf2.png
          pf2.png
          103 kB
        8. pf3.png
          pf3.png
          43 kB
        9. pf4.png
          pf4.png
          86 kB
        10. post_functions.png
          post_functions.png
          39 kB
        11. screenshotarea20180209121624.png
          screenshotarea20180209121624.png
          71 kB
        12. sprint_report_01.png
          sprint_report_01.png
          44 kB
        13. sprint_report_01b.png
          sprint_report_01b.png
          55 kB
        14. sprint_report_01c.png
          sprint_report_01c.png
          55 kB
        15. sprint_report_01d.png
          sprint_report_01d.png
          44 kB
        16. sprint_report_01e.png
          sprint_report_01e.png
          50 kB
        17. sprint_report_02.png
          sprint_report_02.png
          15 kB
        18. sprint_report_02b.png
          sprint_report_02b.png
          23 kB
        19. sprint_report_02c.png
          sprint_report_02c.png
          69 kB
        20. useless_burndown.png
          useless_burndown.png
          14 kB

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

                Created:
                Updated:
                Resolved: