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

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