test plan:
* set your clock to the future
* run CountsReport
* set your clock to the present
* ensure graphs on the statistics page don't take the future into
account
Change-Id: Ibcd0403fdd504a6a646e4a84b45203d98469bda9
Reviewed-on: https://gerrit.instructure.com/11127
Tested-by: Jenkins <jenkins@instructure.com>
Reviewed-by: Jeremy Stanley <jeremy@instructure.com>
basically for detailed reports, have a row per account, instead of
stuffing everything into one massive hash with every account
test plan:
* ensure that the account statistics page still works
* ensure that the statistics update when the delayed job runs
Change-Id: I2d4c9ff5a86c8df6d82097aa4f0203a0f55ddb2d
Reviewed-on: https://gerrit.instructure.com/9565
Reviewed-by: Simon Williams <simon@instructure.com>
Tested-by: Cody Cutrer <cody@instructure.com>