[MGNLPN-104] Adding & removing a segment to a variant leaves an empty property "mgnl:assignedSegments" causing problems for variant resolution Created: 12/May/14  Updated: 01/Oct/20  Resolved: 19/May/14

Status: Closed
Project: Magnolia Personalization
Component/s: Integration, Segmentation App
Affects Version/s: None
Fix Version/s: 1.0

Type: Bug Priority: Neutral
Reporter: Philip Mundt Assignee: Philip Mundt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLUI-2891 MultiValueField should not persist em... Closed
relation
is related to MGNLPN-614 jcrMultipropertyValue is not removed ... 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
Epic Link: Personalisation

 Description   

To reproduce:

  • Create segment
  • Assign it to a variant
    • Check the "mgnl:assignedSegments" exists
  • Remove the segment (make sure there is no other segment assigned)
    • Check the "mgnl:assignedSegments" still exists (empty) although it shouldn't


 Comments   
Comment by Philip Mundt [ 14/May/14 ]

The problem comes from a small error in info.magnolia.ui.form.field.transformer.multi.MultiValueTransformer

Comment by Philip Mundt [ 14/May/14 ]

Whenever magnolia_ui with the fix is released, update the dependency to it accordingly (5.3-m8).

Generated at Mon Feb 12 06:34:20 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.