Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-90321

The Sprint Health gadget does not estimate Scope Change at all when Scope Change has occurred

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Summary

      The Sprint Health gadget is not correctly reporting Scope Change when changes have been made to the Original / Remaining Time Estimates within a Sprint

      Environment

      Cloud 1000.285.1

      Steps to Reproduce

      1. Create a new Sprint
      2. Create several issues
      3. Add Original / Remaining Time Estimates to the issues
      4. Add these issues to the Sprint
      5. Start the Sprint
      6. Create several more issues
      7. Estimate these issues the same way you did the original issues
      8. Add these new issues to the Sprint
      9. Confirm the Scope Change
      10. Add the Sprint Health gadget to a Dashboard

      Expected Results

      The Sprint Health gadget should display relevant information based on the sprint. The Scope Change should read something other than 0%

      Actual Results

      The Sprint Health gadget displays 0% for the Scope Change

      Notes

      When setting this up, make sure that your Estimation configuration is set for Original Time Estimate within your board as well

      Workaround

      There is no work around currently

              Unassigned Unassigned
              aa173e867c9c Akhil Karun (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: