Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-65177

Allow users to customise how often the upcoming activities due insights are generated

    XMLWordPrintable

    Details

    • Testing Instructions:
      Hide
      1. Log in as admin
      2. Go to site admin > analytics > analytics settings and untick onlycli setting
      3. Go to site admin > analytics > analytics models
      4. Click on Actions > Edit for No teaching model
      5. You should see a form with just 2 fields: an enable/disable checkbox and a select for time-splitting methods.
      6. Change the time-splitting method to Upcoming 3 days and save changes
      7. You SHOULD see Upcoming 3 days in the models list page
      8. Change the time-splitting method back to Single range and save changes
      9. You SHOULD NOT have a Delete option for the No teaching model
      10. Click on Actions > Edit for the Students at risk of dropping out model
      11. You SHOULD see the following fields: enabled, indicators, time-splitting method and predictions processor
      12. You SHOULD have a Delete option for the Students at risk of dropping out model, click on the Delete option and confirm the deletion
      13. Create a new model by clicking on Create model buttom
      14. You SHOULD see the following fields: enabled, target, indicators, time-splitting method and predictions processor
      15. Select a target, a time-splitting method and a predictions processor. Try to save changes
      16. You SHOULD see a This model does not have any indicators error
      17. Select a bunch of indicators. You SHOULD now be able to save changes and the new model SHOULD appear in the models list
      Show
      Log in as admin Go to site admin > analytics > analytics settings and untick onlycli setting Go to site admin > analytics > analytics models Click on Actions > Edit for No teaching model You should see a form with just 2 fields: an enable/disable checkbox and a select for time-splitting methods. Change the time-splitting method to Upcoming 3 days and save changes You SHOULD see Upcoming 3 days in the models list page Change the time-splitting method back to Single range and save changes You SHOULD NOT have a Delete option for the No teaching model Click on Actions > Edit for the Students at risk of dropping out model You SHOULD see the following fields: enabled, indicators, time-splitting method and predictions processor You SHOULD have a Delete option for the Students at risk of dropping out model, click on the Delete option and confirm the deletion Create a new model by clicking on Create model buttom You SHOULD see the following fields: enabled, target, indicators, time-splitting method and predictions processor Select a target, a time-splitting method and a predictions processor. Try to save changes You SHOULD see a This model does not have any indicators error Select a bunch of indicators. You SHOULD now be able to save changes and the new model SHOULD appear in the models list
    • Affected Branches:
      MOODLE_37_STABLE
    • Fixed Branches:
      MOODLE_37_STABLE
    • Pull from Repository:
    • Pull Master Branch:
      MDL-65177_master

      Description

      We have two possible approaches here:

      1. We add a couple more time-splitting methods to core so people is not limited to weekly insights. We could have 'weekly' and something like 'every 3 days' and 'every fortnight'. The upcoming activities due insight is based on assumptions and we don't allow users to edit these models because they can mess up the indicators list. We could allow users to edit models based on assumptions, but only the time splitting method they use.
      2. We could add a UI so people can customise when predictions are generated and the time frame use to calculate indicators.

      The 2nd option is obviously better, although we are 2 weeks away from the code freeze and I am not sure if we have enough time for it.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  20/May/19

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 hour, 35 minutes
                  1h 35m