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

Add bulk actions to the Privacy Request Table

    XMLWordPrintable

    Details

    • Testing Instructions:
      Hide

      Test in Boost and Clean.

      Pre-requisites

      1. Upgrade your Moodle instance to the latest version.
      2. Create 2 Users (user1, user2).
      3. Login as user1.
      4. Go to 'Profile' > 'Data requests'.
      5. Create 2 new requests.
        1. Export data request.
        2.  Delete data request.
      6. Login as user2.
      7. Go to 'Profile' > 'Data requests'.
      8. Create 2 New requests.
      9. Export data request.
      10. Delete data request.
      11. Run the cron. ('php admin/cli/cron.php')

      Test 1 (Elements are properly rendered)

      1. Login as Admin or a DPO.
      2. Go to 'Site administration' > 'Users' > 'Data requests'.
        • make sure the requests created by user1 and user2 are displayed in the table with 'Awaiting approval' status.
        • make sure a checkbox element is available for each request that has 'Awaiting approval' status.
        • make sure there is a select element with the available bulk actions and a confirm button at the bottom of the requests table.

      Test 2 (Validation).

      1. Login as Admin or a DPO.
      2. Go to 'Site administration' > 'Users' > 'Data requests'.
      3. Make sure that proper pop-up notifications are displayed when the bulk request is invalid. Test this with several scenarios such as:
        • press on the 'Confirm' button, without previouly selecting any bulk actions and without checking any data requests.
        • press on the 'Confirm' button, with selected bulk action (ex. 'Approve') and without checking any data requests.
        • etc.

      Test 3 (Bulk actions)

      1. Login as Admin or a DPO.
      2. Go to 'Site administration' > 'Users' > 'Data requests'.
      3. Check several data request from the data requests table that are awaiting for approval.

      Repeat these steps for both bulk actions ('Approve/Deny')

      1. Select a bulk action from the select element (ex. 'Approve').
      2. Press the 'Confirm button'.
        • make sure a pop-up is displayed asking to confirm the bulk action.
      3. Confirm the bulk action.
      4. Make sure the bulk action has been properly applied to all of the selected data requests.

      Test 4 (Number of data request per page)

      1. Login as Admin or a DPO.
      2. Create multiple data requests. (more than 50 at least).
      3. Go to 'Site administration' > 'Users' > 'Data requests'.
        • make sure you can see the 'Per page' select box at the bottom of the requests table.
      4. Select different values for "Per page".
        • make sure everything works as expected and the correct number of data request is displayed in the table

       

      Show
      Test in Boost and Clean. Pre-requisites Upgrade your Moodle instance to the latest version. Create 2 Users (user1, user2). Login as user1. Go to 'Profile' > 'Data requests'. Create 2 new requests. Export data request.  Delete data request. Login as user2. Go to 'Profile' > 'Data requests'. Create 2 New requests. Export data request. Delete data request. Run the cron. ('php admin/cli/cron.php') Test 1 (Elements are properly rendered) Login as Admin or a DPO. Go to 'Site administration' > 'Users' > 'Data requests'. make sure the requests created by user1 and user2 are displayed in the table with 'Awaiting approval' status. make sure a checkbox element is available for each request that has 'Awaiting approval' status. make sure there is a select element with the available bulk actions and a confirm button at the bottom of the requests table. Test 2 (Validation). Login as Admin or a DPO. Go to 'Site administration' > 'Users' > 'Data requests'. Make sure that proper pop-up notifications are displayed when the bulk request is invalid . Test this with several scenarios such as: press on the 'Confirm' button, without previouly selecting any bulk actions and without checking any data requests. press on the 'Confirm' button, with selected bulk action (ex. 'Approve') and without checking any data requests. etc. Test 3  (Bulk actions) Login as Admin or a DPO. Go to 'Site administration' > 'Users' > 'Data requests'. Check several data request from the data requests table that are awaiting for approval. Repeat these steps for both bulk actions ('Approve/Deny') Select a bulk action from the select element (ex. 'Approve'). Press the 'Confirm button'. make sure a pop-up is displayed asking to confirm the bulk action. Confirm the bulk action. Make sure the bulk action has been properly applied to all of the selected data requests. Test 4  (Number of data request per page) Login as Admin or a DPO. Create multiple data requests. (more than 50 at least). Go to 'Site administration' > 'Users' > 'Data requests'. make sure you can see the 'Per page' select box at the bottom of the requests table. Select different values for "Per page". make sure everything works as expected and the correct number of data request is displayed in the table  
    • Affected Branches:
      MOODLE_33_STABLE, MOODLE_34_STABLE, MOODLE_35_STABLE, MOODLE_36_STABLE
    • Fixed Branches:
      MOODLE_33_STABLE, MOODLE_34_STABLE, MOODLE_35_STABLE
    • Epic Link:
    • Pull from Repository:
    • Pull 3.5 Branch:
      MDL-63116-35-1
    • Pull 3.5 Diff URL:
    • Pull Master Branch:
      MDL-63116-master-1
    • Pull Master Diff URL:
    • Sprint:
      GDPR Followup Sprint 1

      Description

      We should add the ability to perform bulk actions on the Data Privacy tool's request page.

      The actions we need to support in bulk are:

      1. Approve
      2. Reject
      3. Cancel

      This will make management of requests far easier.

        Attachments

        1. 1.PNG
          1.PNG
          184 kB
        2. 2.PNG
          2.PNG
          153 kB

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved:
                Fix Release Date:
                12/Nov/18

                Time Tracking

                Estimated:
                Original Estimate - 0 minutes
                0m
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 2 hours, 30 minutes
                2h 30m