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

User delete request status switches from confirmed to rejected

    XMLWordPrintable

    Details

    • Testing Instructions:
      Hide
      1. Create a brand new site with a course and users enrolled in the course
      2. Create a forum in the course
      3. Post as a test user in the forum
      4. Login as admin
      5. Navigate to Site admin => Users => Data requests
      6. Create a new export request for that user
      7. Run cron
      8. Approve the request
      9. Run cron
      10. Refresh the data requests page
        1. Confirm the Download is ready
      11. Create a new delete request for that user
      12. Run cron
      13. Approve the request
      14. Run cron
      15. Refresh the data requests page
        1. Confirm the user was deleted
      Show
      Create a brand new site with a course and users enrolled in the course Create a forum in the course Post as a test user in the forum Login as admin Navigate to Site admin => Users => Data requests Create a new export request for that user Run cron Approve the request Run cron Refresh the data requests page Confirm the Download is ready Create a new delete request for that user Run cron Approve the request Run cron Refresh the data requests page Confirm the user was deleted
    • Affected Branches:
      MOODLE_35_STABLE, MOODLE_36_STABLE
    • Fixed Branches:
      MOODLE_34_STABLE, MOODLE_35_STABLE
    • Pull 3.5 Branch:
    • Pull Master Branch:
      MDL-64030-master

      Description

      Moodle [3.5.3 (Build: 20181112)|http://docs.moodle.org/dev/Releases]

      A user send message that the account should be deleted.
      The DPO confirmes.
      In overview the status switches to confirmed
      After next cron the status switches to rejected.

      Its not possible to delete the account finally through privacy API.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                2 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  14/Jan/19

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 30 minutes
                  30m