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

Data requests should be sorted by ascending status and request date

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 3.5
    • Fix Version/s: 3.5
    • Component/s: Privacy
    • Labels:
    • Testing Instructions:
      Hide
      1. Login as a user s1.
      2. Go to your user profile.
      3. Click on Data requests and create a new export data request r1-1.
      4. Cancel the request.
      5. Create another request r1-2 for s1.
      6. Login as another user s2 and create a data request r2.
      7. Run cron.

        php admin/cli/cron.php

      8. Login as another user s3 and create a data request r3
      9. Login as admin and go to "Site administration / Privacy and policies / Data requests"
      10. Confirm that the requests are listed in the following order: r3 (Pending), r1-2 (Awaiting approval), r2 (Awaiting approval), r1-1 (Cancelled).
      11. View s1's request and approve it.
      12. Confirm that the requests are listed in the following order: r3 (Pending), r2 (Awaiting approval), r1-2 (Approved), r1-1 (Cancelled).
      13. Run cron again.
      14. Refresh the data requests page.
      15. Confirm that the requests are listed in the following order: r2 (Awaiting approval), r3 (Awaiting approval), r1-2 (Complete), r1-1 (Cancelled).

      Bottom line is:

      • The request in the early stage of the process should be the first on the list.
      • For requests with the same status, the request which was made earlier should be shown before the later requests.
      Show
      Login as a user s1. Go to your user profile. Click on Data requests and create a new export data request r1-1. Cancel the request. Create another request r1-2 for s1. Login as another user s2 and create a data request r2. Run cron. php admin/cli/cron.php Login as another user s3 and create a data request r3 Login as admin and go to " Site administration / Privacy and policies / Data requests " Confirm that the requests are listed in the following order: r3 (Pending), r1-2 (Awaiting approval), r2 (Awaiting approval), r1-1 (Cancelled). View s1's request and approve it. Confirm that the requests are listed in the following order: r3 (Pending), r2 (Awaiting approval), r1-2 (Approved), r1-1 (Cancelled). Run cron again. Refresh the data requests page. Confirm that the requests are listed in the following order: r2 (Awaiting approval), r3 (Awaiting approval), r1-2 (Complete), r1-1 (Cancelled). Bottom line is: The request in the early stage of the process should be the first on the list. For requests with the same status, the request which was made earlier should be shown before the later requests.
    • Affected Branches:
      MOODLE_35_STABLE
    • Fixed Branches:
      MOODLE_35_STABLE
    • Pull Master Branch:
      MDL-62209-master

      Description

      DPOs should see data requests in FIFO order. Seeing data requests piled at the bottom of the list is not a very good user experience.

        Attachments

          Activity

            People

            • Assignee:
              jpataleta Jun Pataleta
              Reporter:
              jpataleta Jun Pataleta
              Peer reviewer:
              Juan Leyva
              Integrator:
              Andrew Nicols
              Tester:
              Helen Foster
              Participants:
              Component watchers:
              Andrew Nicols, Jun Pataleta, Michael Hawkins, Shamim Rezaie, Simey Lameze
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Fix Release Date:
                17/May/18