[Rt-commit] rt branch, 4.4/add-gdpr-docs, repushed

[Jim Brandt]

The branch 4.4/add-gdpr-docs was deleted and repushed:
       was 13ef1853199e28c4dbe88c00d0e864237a0b602b
       now 80aca50eaa8ff106a6142df4caec4453362e9ee0

1: 13ef185319 ! 1: 80aca50eaa Add GDPR docs
    @@ -94,7 +94,7 @@
     +
     +One provision of GDPR gives users the "right to be forgotten" which means they can
     +request that their data be removed from an organization's system. RT provides several
    -+options to remove data associated with a user. These use the L<RT::Shredder> tool, but
    ++options to remove data associated with a user. These use the L<RT::Shredder> tool and
     +links are provided from the user administration page to make removal easier.
     +
     +=head2 Anonymize User
    @@ -107,7 +107,7 @@
     +email address, stored on the user record is removed.
     +
     +It is important to note that this action will not remove user information
    -+from ticket bodies or email headers, only data from any RT-based sections like
    ++from ticket message bodies or email headers, only data from any RT-based sections like
     +People. To anonymize ticket data, RT provides a script C<rt-munge-attachments>
     +which you should also run. It is not linked from the web UI because it can
     +require a long time to run.
    @@ -116,15 +116,24 @@
     +
     +This option uses shredder with the replace_relations option to replace the
     +existing userid with the RT user "Nobody" in transactions and other records
    -+that have the id. The user record is then completely deleted.
    ++that have the id. The user record is then deleted. This option is likely the
    ++easiest since it automatically handles linked objects in one step.
     +
    -+To replace with a user other than Nobody, update the replace_relations option
    -+once on the shredder page.
    ++To replace with a user other than Nobody, update the replace_relations argument
    ++on the shredder page before running.
     +
     +=head2 Remove User Information
     +
    -+This option uses shredder to completely remove the user and connected data by running
    -+it without the replace option. Note that this option will fail unless linked tickets
    -+and ticket data is shredded before hand. See L<RT::Shredder> for more information.
    ++This option uses shredder to remove the user record by running shredder
    ++it without the replace option. Note that this option will fail unless if it
    ++finds remaining references to the user. For example, if the user is a requestor
    ++on a ticket and the ticket is still in the system, the user will still be connected
    ++to the ticket, transactions on the ticket, etc.
    ++
    ++To resolve this, you can use other shredder plugins to first remove the other
    ++associated objects. For tickets, for example, you could run a search for
    ++"RequestorEmail = 'user1 at example.com'" and then shred the tickets returned.
    ++Once the associated objects are shredded, you can try shredding the user again.
    ++See L<RT::Shredder> for information on plugins for other objects.
     +
     +=cut