• We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      The documentation for the Sprint Health Gadget currently doesn't explain the logic behind the scope change. It appears to be an approximate percentage of plus or minus change in the total story points of a sprint, but doesn't reflect any change when you simply delete story points or replace the value with a blank in any tasks.

      Basically, users are confused about the logic of this calculation, without any clear documentaion on it.

            [JSWSERVER-9681] Document the 'Scope Change' calculation logic

            First time setting up a sprint and there was a little learning curve. Is there any way to change the scope % to 0? 

            Nancy Corsi added a comment - First time setting up a sprint and there was a little learning curve. Is there any way to change the scope % to 0? 

            Michael Tanner added a comment - - edited

            Andrew, could you please update your link? I'm keen to see how to do that, but it appears the link points at a general tutorial.

             

            UPDATE: I think you intended to point [here|https://confluence.atlassian.com/jirasoftwareserver/configuring-estimation-and-tracking-938845319.html].

            Michael Tanner added a comment - - edited Andrew, could you please update your link? I'm keen to see how to do that, but it appears the link points at a general tutorial.   UPDATE: I think you intended to point [here| https://confluence.atlassian.com/jirasoftwareserver/configuring-estimation-and-tracking-938845319.html ].

            Andrew added a comment -

            Here's what was documented in the original page:

            Adding or removing an issue from a sprint, after it has started is considered a change of scope. The percentage is calculated using the statistic that is configured for the board (see Configuring Estimation and Tracking).

            For example, if you started a sprint with 50 story points and add an issue with 5 story points, the Sprint Health gadget would show a 10% scope change.

            If you add/remove issues that don't have estimates, the scope change will not be altered.

            If you're using Time Tracking, Scope Change will not be shown.

            Andrew added a comment - Here's what was documented in the original page: Adding or removing an issue from a sprint, after it has started is considered a change of scope. The percentage is calculated using the statistic that is configured for the board (see  Configuring Estimation and Tracking ). For example, if you started a sprint with 50 story points and add an issue with 5 story points, the Sprint Health gadget would show a 10% scope change. If you add/remove issues that don't have estimates, the scope change will not be altered. If you're using Time Tracking, Scope Change will not be shown.

            alui, Do you have a new link or can you explain the formula behind the scope change % in the Sprint Health Gadget?

            The percentage is still not reliable for me.

            Kevin Colijn added a comment - alui , Do you have a new link or can you explain the formula behind the scope change % in the Sprint Health Gadget? The percentage is still not reliable for me.

            Oren Weiss added a comment -

            Hi , The link does not work anymore. 

            Oren Weiss added a comment - Hi , The link does not work anymore. 

            Andrew added a comment -

            Andrew added a comment - See https://confluence.atlassian.com/pages/diffpages.action?pageId=391087262&originalId=395707021

            alui can you please take a look?

            Michael Tokar added a comment - alui can you please take a look?

              alui Andrew
              takindele Taiwo Akindele (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: