-
Type:
Bug
-
Status: Verified
-
Resolution: Unresolved
-
Affects Version/s: Master
-
Fix Version/s: None
-
Component/s: Collections > Collections Personalization
-
Labels:
-
Fix Priority:3
-
Sprint:TANGO | #73 DEV | Feb04-Feb25
-
Git Pull Request:
Description:
Anyone collection doesn't follow a right behaviour in Content Sets
Steps to reproduce:
Given a user belonging to Segment 1 and Segment 2
And the configuration to combine assets is enabled
When there's a variation of a manual collection targeting segment 1 and segment 2, and both are prioritized above the anyone variation
Then the user will see the assets included in both variations targeting segments in Asset Publisher / Collection Display Fragment
Actual Result - The assets in both variations AND the Anyone variation is shown.
Given a user who does not belong to any Segment
And the configuration to combine assets is enabled
When there's a variation of a dynamic collection targeting segment 1 and segment 2, and both are prioritized above the anyone variation
Then the user will see the assets included in the Anyone Variation in Asset Publisher / Collection Display Fragment
Actual Result - No assets are displayed in the Asset Publisher / Collection Display Fragment
Acceptance Criteria
Acceptance Criteria | Test Strategy |
---|---|
|
Medium |
|
Medium |
|
Medium |
|
Medium |
- is caused by
-
LPS-141797 As a content manager, I want the order of collections variations to determine the priority in which they're presented to the users in the matching segments
-
- Closed
-