Activity log for bug #1734182

Date Who What changed Old value New value Message
2017-11-23 18:40:54 Kristina Hoeppner bug added bug
2017-11-23 19:08:09 Kristina Hoeppner description We need to make a series of changes in Mahara to comply with the GDPR. More info is available on the wiki at https://wiki.mahara.org/wiki/Developer_Area/Specifications_in_Development/GDPR_compliance We need to keep old versions of the T&C and consents and show them to administrators and also users. See bug #1734171 for an idea for displaying them to a user. Site and institution administrators could view theirs in the admin area's "Privacy" section. They would be listed in reverse chronological order starting with the current live version. Institution admins would be able to see the site T&C as well as they may need to refer to them in order to know what specific items they may need to cover in their institution T&C. Admins can create new T&C (but not revert or edit existing ones). We need to make a series of changes in Mahara to comply with the GDPR. More info is available on the wiki at https://wiki.mahara.org/wiki/Developer_Area/Specifications_in_Development/GDPR_compliance We need to keep old versions of the T&C and consents and show them to administrators and also users. See bug #1734171 for an idea for displaying them to a user. Site and institution administrators could view theirs in the admin area's "Privacy" section. They would be listed in reverse chronological order starting with the current live version. Institution admins would be able to see the site T&C as well as they may need to refer to them in order to know what specific items they may need to cover in their institution T&C. Admins can create new T&C (but not revert or edit existing ones). Each version needs to be directly accessible from an admin report (and also in the user's settings; see bug #1734171). Wishlist item for the admin report: bug #1734188
2017-11-28 14:33:28 Mark Webster bug added subscriber Mark Webster
2017-12-01 16:16:03 Maria Sorica mahara: assignee Maria (maria-sorica)
2017-12-21 00:23:46 Kristina Hoeppner mahara: status Confirmed In Progress
2017-12-26 21:56:15 Kristina Hoeppner summary Keep old versions of the T&C and make them available Keep old versions of the privacy statement and make them available
2017-12-26 21:56:49 Kristina Hoeppner description We need to make a series of changes in Mahara to comply with the GDPR. More info is available on the wiki at https://wiki.mahara.org/wiki/Developer_Area/Specifications_in_Development/GDPR_compliance We need to keep old versions of the T&C and consents and show them to administrators and also users. See bug #1734171 for an idea for displaying them to a user. Site and institution administrators could view theirs in the admin area's "Privacy" section. They would be listed in reverse chronological order starting with the current live version. Institution admins would be able to see the site T&C as well as they may need to refer to them in order to know what specific items they may need to cover in their institution T&C. Admins can create new T&C (but not revert or edit existing ones). Each version needs to be directly accessible from an admin report (and also in the user's settings; see bug #1734171). Wishlist item for the admin report: bug #1734188 We need to make a series of changes in Mahara to comply with the GDPR. More info is available on the wiki at https://wiki.mahara.org/wiki/Developer_Area/Specifications_in_Development/GDPR_compliance We need to keep old versions of the privacy statement and consents and show them to administrators and also users. See bug #1734171 for an idea for displaying them to a user. Site and institution administrators could view theirs in the admin area's "Privacy" statement section. They would be listed in reverse chronological order starting with the current live version. Institution admins would be able to see the site privacy statement as well as they may need to refer to them in order to know what specific items they may need to cover in their institution privacy statement. Admins can create a new privacy statement (but not revert or edit existing ones). Each version needs to be directly accessible from an admin report (and also in the user's settings; see bug #1734171). Wishlist item for the admin report: bug #1734188
2018-01-12 09:13:30 Maria Sorica mahara: status In Progress Fix Committed
2018-02-09 05:23:03 Kristina Hoeppner tags gdpr gdpr nominatedfeature
2018-04-05 23:02:52 Robert Lyon mahara: status Fix Committed Fix Released