[MGNLPN-156] Enable setting AND/OR operand in trait aggregator Created: 10/Jun/14 Updated: 17/Jun/14 Resolved: 16/Jun/14 |
|
| Status: | Closed |
| Project: | Magnolia Personalization |
| Component/s: | Integration |
| Affects Version/s: | None |
| Fix Version/s: | 1.0 |
| Type: | New Feature | Priority: | Critical |
| Reporter: | Mikaël Geljić | Assignee: | Mikaël Geljić |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | traitchooser | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Template: |
|
||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||
| Epic Link: | Personalisation | ||||||||||||
| Description |
|
| Comments |
| Comment by Mikaël Geljić [ 11/Jun/14 ] |
| Comment by Mikaël Geljić [ 11/Jun/14 ] |
|
Ouch, hard-coding introductory Labels inside SegmentationMultiField or TraitAggregatorMultiField actually breaks the inherited logic from MultiField: |