When a related list has an encrypted field (say short description), it shows the gibberish value for unauthorized users instead of empty/blank value
Release or Environment
If field encryption is created on a child table (say incident) but the relationship of the related list is defined to pull data from the parent table (say task), this causes the related lists to show gibberish value in the encrypted field for unauthorized users instead of empty/blank value
Though 'task' is the parent table, it does not have enough data de-crypt the field and hence the relationship of the related lists should be defined on the child tables holding the encryption context.
To resolve the issue, change the relationship of the related lists to point to the table on which the field encryption exists i.e, the child table in this context.