-
Bug
-
Resolution: Fixed
-
High (View bug fix roadmap)
-
None
-
None
NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.
The calculation of the scope change is sometimes not correct.
Steps to reproduce
- Create a sprint in Plan Mode
- Create 5 issues with an estimate of '2' each.
- Add all 5 issues to the future sprint.
- Remove one of the issues from the future sprint.
- Start the sprint with the remaining 4 issues.
- Look at the Sprint Health Gadget - the scope change amount will be 0%.
- Remove another issue from the sprint.
- Look at the Sprint Health Gadget again.
Expected
The scope change amount should be -25% – 8 points originally in scope, and 2 were removed.
Actual
The scope change amount is -40%.
- is caused by
-
JSWSERVER-9797 Issue moved out of sprint before start, still shows on reports
-
- Closed
-
- is related to
-
JSWSERVER-9790 Sprint Report does not include Story Points added to a Planned Sprint
-
- Closed
-
-
JSWSERVER-11334 Sprint report does not include story points added to a started sprint
-
- Closed
-
- relates to
-
JSWCLOUD-9783 Sprint Health Gadget scope change calculation is incorrect
-
- Closed
-
-
JST-75641 You do not have permission to view this issue
- Testing discovered
-
JSWSERVER-9885 Sprint Health Gadget appears to double count scope change
-
- Closed
-
[JSWSERVER-9783] Sprint Health Gadget scope change calculation is incorrect
Workflow | Original: JAC Bug Workflow v2 [ 2850750 ] | New: JAC Bug Workflow v3 [ 2933818 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545410 ] | New: JAC Bug Workflow v2 [ 2850750 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1551817 ] | New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545410 ] |
Description |
Original:
The calculation of the scope change is sometimes not correct. h3. Steps to reproduce # Create a sprint in Plan Mode # Create 5 issues with an estimate of '2' each. # Add all 5 issues to the future sprint. # Remove one of the issues from the future sprint. # Start the sprint with the remaining 4 issues. # Look at the Sprint Health Gadget - the scope change amount will be 0%. # Remove another issue from the sprint. # Look at the Sprint Health Gadget again. h4. Expected The scope change amount should be -25% -- 8 points originally in scope, and 2 were removed. h4. Actual The scope change amount is -40%. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This bug report is for *JIRA Software Server*. Using *JIRA Software Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSWCLOUD-9783]. {panel} The calculation of the scope change is sometimes not correct. h3. Steps to reproduce # Create a sprint in Plan Mode # Create 5 issues with an estimate of '2' each. # Add all 5 issues to the future sprint. # Remove one of the issues from the future sprint. # Start the sprint with the remaining 4 issues. # Look at the Sprint Health Gadget - the scope change amount will be 0%. # Remove another issue from the sprint. # Look at the Sprint Health Gadget again. h4. Expected The scope change amount should be -25% -- 8 points originally in scope, and 2 were removed. h4. Actual The scope change amount is -40%. |
Link |
New:
This issue relates to |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 909559 ] | New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1551817 ] |
Workflow | Original: GreenHopper Kanban Workflow 20141014 [ 746923 ] | New: JIRA Bug Workflow w Kanban v6 [ 909559 ] |
Workflow | Original: GreenHopper Kanban Workflow v2 [ 555156 ] | New: GreenHopper Kanban Workflow 20141014 [ 746923 ] |
Hi,What is the logical formula used to calculate scope change in the Sprint Health Gadget? please help me understand !!!! Thanks !!!!