Details
-
Story
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
-
Empty show more show less
-
Add-Ons 34
-
5
Description
Open questions
- Should we automatically generate variants when the original page has been selected?
- How the behaviour should be when one selects another original page?
- When an original page has existing variants, what will happen?
- Will we show them?
Agreed on the `Simple and more user friendly` variant:
- Automatically generate an original variant when test starts. (
ABTEST-140)- Consistency check on the run action whether , there must be a ticket for that somewhere (
ABTEST-141)
- Consistency check on the run action whether , there must be a ticket for that somewhere (
- We don’t create a variant automatically, user is in full charge/control over it.
- What about locking the node when it is in the test setup (without starting?) (
ABTEST-171)- This way, we don’t have the must to check consistency of the original node over time. (potential changes and stale variants)
- When someone changes the original page (from the selector), what is the fate of the redundant variants? (
ABTEST-140)- We keep the variants until the test has been finally started. (then we collect/remove the stale ones)
- Remove the variants once only the test has started and we know for sure the variants are generated from that test
- When an original page has existing variants (personalisation), what will happen?
- It is not part of MVP but ticketed
- Ignore the variants for the time being
Checklists
Acceptance criteria
Attachments
Issue Links
- is depended upon by
-
ABTEST-140 Create Variant A (original) on test start based on originalPage value
-
- Closed
-
-
ABTEST-152 Reserve
-
- Closed
-