Uploaded image for project: 'Moodle app'
  1. Moodle app
  2. MOBILE-3975

Move the default notification time for calendar events to config.json

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.9.5
    • 4.0.0
    • Others
    • Hide

      This issue only needs to be tested in 1 device.

      Test default value

      1. Install the 3.9.5 app in a device.
      2. Login in a site that has at least 1 calendar event. We'll call this user u1.
      3. Go to Calendar > Top-right menu > Settings.
      4. Change the Default notification time to whatever you want.
      5. Go back and open any event. Check that the default reminder says the time you set in the previous step.
      6. Now login in the same site with another user. We'll call this user u2.
      7. Go to Calendar and open any event. Check that the default reminder says 1 hour.
      8. Now install the app with this patch applied.
      9. As u2, open any calendar event. Check that the default reminder still says 1 hour.
      10. Now logout as u1 and open any calendar event. Check that the default reminder says the time you set in step 4.

      Test custom value (for BMAs)

      1. Repeat steps 1-7.
      2. Create a build changing the value of "calendarreminderdefaultvalue" to any value (make sure it's different from the one used for u1 in the previous steps). You can also change the value from config.json dynamically from the console, but please notice that in that case the local notifications might not trigger at the right time (they can be scheduled before you change the value).
      3. As u2, open any calendar event. Check that the default reminder now says the time you set in config.json.
      4. Now logout as u1 and open any calendar event. Check that the default reminder says the time you set in previous steps.
      Show
      This issue only needs to be tested in 1 device. Test default value Install the 3.9.5 app in a device. Login in a site that has at least 1 calendar event. We'll call this user u1. Go to Calendar > Top-right menu > Settings. Change the Default notification time to whatever you want. Go back and open any event. Check that the default reminder says the time you set in the previous step. Now login in the same site with another user. We'll call this user u2. Go to Calendar and open any event. Check that the default reminder says 1 hour. Now install the app with this patch applied. As u2, open any calendar event. Check that the default reminder still says 1 hour. Now logout as u1 and open any calendar event. Check that the default reminder says the time you set in step 4. Test custom value (for BMAs) Repeat steps 1-7. Create a build changing the value of "calendarreminderdefaultvalue" to any value (make sure it's different from the one used for u1 in the previous steps). You can also change the value from config.json dynamically from the console, but please notice that in that case the local notifications might not trigger at the right time (they can be scheduled before you change the value). As u2, open any calendar event. Check that the default reminder now says the time you set in config.json. Now logout as u1 and open any calendar event. Check that the default reminder says the time you set in previous steps.
    • MOODLE_39_STABLE
    • MOODLE_400_STABLE
    • Moodle App 4.0

    Description

      Move the default notification time for calendar events to config.json, so it can be configured for specific sites/BMAs

      Attachments

        1. screenshot-4.png
          screenshot-4.png
          76 kB
        2. screenshot-3.png
          screenshot-3.png
          76 kB
        3. screenshot-2.png
          screenshot-2.png
          72 kB
        4. screenshot-1.png
          screenshot-1.png
          71 kB

        Activity

          People

            dpalou Dani Palou
            jleyva Juan Leyva
            Pau Ferrer Pau Ferrer
            Juan Leyva Juan Leyva
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              22/Apr/22