[MGNLPRIV-39] Prune of JCR references works only if consent group and field name matches Created: 26/Jun/18  Updated: 30/Jan/23  Resolved: 30/Jan/23

Status: Closed
Project: Privacy
Component/s: None
Affects Version/s: 1.0
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Roman Kovařík Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MGNLPRIV-38 AddConsentFormProcessor should provid... Closed
is cloned by MGNLPRIV-40 Visitor deletion should tell you the ... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: Data privacy 1
Team: AdminX

 Description   

To reproduce:

  1. Create a reference with an email (e.g via the travel demo contact form)
  2. Confirm consent trough the confirmation email or via the visitors app.
  3. Remove consent for email via visitors app.
  4. Check reference: email property is deleted.
  5. Create a new consent group, e.g. config:visitor-manager/config/personal-fields/details/message=message
  6. Go to the contact form, now it should require consent for the details group.
  7. Confirm consent.
  8. Remove consent for the details group.
  9. Check the reference, the message property is not deleted.


 Comments   
Comment by Matt Rajkovic [ 30/Jan/23 ]

Very old issue. Closing.

Generated at Mon Feb 12 10:31:03 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.