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

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

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

      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
      Server Current

      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

            [JSWSERVER-14757] The Sprint Health gadget does not estimate Scope Change at all when Scope Change has occurred

            We are experiencing this issue on Jira 8.20.

             

            Shekhar Kanodia added a comment - We are experiencing this issue on Jira 8.20.  

            Anna Przybycień added a comment - - edited

            Hi all, I believe this issue is duplicated by https://jira.atlassian.com/browse/JRASERVER-71708, which is fixed on Jira 8.13.1. I followed reproduction steps to confirm and the bug does not reproduce on Jira 8.13.1. Could anyone confirm/debunk this theory? Anyone experiencing this bug while on Jira 8.13.1+?

            Anna Przybycień added a comment - - edited Hi all, I believe this issue is duplicated by https://jira.atlassian.com/browse/JRASERVER-71708 , which is fixed on Jira 8.13.1. I followed reproduction steps to confirm and the bug does not reproduce on Jira 8.13.1. Could anyone confirm/debunk this theory? Anyone experiencing this bug while on Jira 8.13.1+?

            Same issue on version 8.7.1#807001-sha1:03e3702 (server)

            Scope change is always 0%

            Jean-Pierre Froud added a comment - Same issue on version 8.7.1#807001-sha1:03e3702 (server) Scope change is always 0%

            Paul Laberge added a comment - - edited

            Hi,

             If you copy your Team Board and set the time tracking to none, it should show the scope change. I create 2 boards for my teams, one for my Scrum Sprints and another (configured with no time tracking) for the health Gadget.

            Paul Laberge added a comment - - edited Hi,  If you copy your Team Board and set the time tracking to none, it should show the scope change. I create 2 boards for my teams, one for my Scrum Sprints and another (configured with no time tracking) for the health Gadget.

            Same problem.

            Lukas Nothdurfter added a comment - Same problem.

            Same problem with my company and Scrum team 
            Any idea when to solve this ? 

            Issam Houidi added a comment - Same problem with my company and Scrum team  Any idea when to solve this ? 

            Same problem for my company.  Please raise priority.

            Neil Gutkind added a comment - Same problem for my company.  Please raise priority.

            Same problem in my company. Guys, 4 years for bug already. You don't has so much gadgets. Why the priority is Low?

            Avenir Voronov added a comment - Same problem in my company. Guys, 4 years for bug already. You don't has so much gadgets. Why the priority is Low?

            Same problem in my company. Management is looking at the Sprint Health dashboard !

            Olivier Magand added a comment - Same problem in my company. Management is looking at the Sprint Health dashboard !

            Same problem in our company. It would be nice to have it fixed.. Raported in 2016...

            Krzysztof Bartosiewicz added a comment - Same problem in our company. It would be nice to have it fixed.. Raported in 2016...

              Unassigned Unassigned
              mlavender mlavender (Inactive)
              Affected customers:
              107 This affects my team
              Watchers:
              84 Start watching this issue

                Created:
                Updated:
                Resolved: