[MGNLPN-325] Don't allow subsegments Created: 01/Sep/16 Updated: 09/Dec/16 Resolved: 09/Dec/16 |
|
| Status: | Closed |
| Project: | Magnolia Personalization |
| Component/s: | Segmentation App |
| Affects Version/s: | 1.2.6 |
| Fix Version/s: | 1.2.9, 1.3.2, 1.4.1 |
| Type: | Bug | Priority: | Major |
| Reporter: | Antti Hietala | Assignee: | Evzen Fochr |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 3h 35m | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| 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
|
||||
| Release notes required: |
Yes
|
||||
| Documentation update required: |
Yes
|
||||
| Date of First Response: | |||||
| Sprint: | Kromeriz 73 | ||||
| Story Points: | 3 | ||||
| Description |
|
Create action availability conditions that prevent subsegments. Prevent adding a segment under another segment. Prevent moving a segment under another segment. A subsegment hierarchy leads to the wrong conclusion that segments apply in a cascading manner – they don't.
1 Does not mean "Registered user from US". It just means "Registered user". Adding folders should be allowed, current behavior. |
| Comments |
| Comment by Michael Mühlebach [ 28/Nov/16 ] |
|
Includes update task to warn about pre-existing subsegments. |
| Comment by Antti Hietala [ 28/Nov/16 ] |
|
For release notes: Creating subsegments is disabled Previously you were able to create "subsegments" by placing one segment under another in the Segments app. This structure was misleading because Magnolia does not apply segments in a cascading fashion. It only applies the one segment you select, not its parents. To avoid potentially misleading segment structures, you can no longer add or move one segment under another. Magnolia warns you about subsegments during the update process. We recommend that you organize your segments using a flat structure or folders. Example: United States ├── New-user └── Registered-user (1) 1 Does not mean "United States AND Registered user". It just means "Registered user". |