[ABTEST-153] Dispatcher should take audience and traffic allocation into account Created: 03/Mar/20 Updated: 17/Apr/20 Resolved: 20/Mar/20 |
|
| Status: | Closed |
| Project: | A/B Testing |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0 |
| Type: | Story | Priority: | Neutral |
| Reporter: | Ilgun Ilgun | Assignee: | Andrei Ichimescu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 0.25d | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Epic Link: | Testing dispatcher |
| Sprint: | Add-Ons 33, Add-Ons 34 |
| Story Points: | 5 |
| Description |
|
Currently, we have a dispatcher strategy that doesn't take traffic allocation or audience selection into consideration.
AC
|