[ABTEST-7] Dispatch content to the correct audience Created: 25/Apr/19 Updated: 25/Sep/19 Resolved: 19/Sep/19 |
|
| Status: | Closed |
| Project: | A/B Testing |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0 |
| Type: | Story | Priority: | Neutral |
| Reporter: | Laura Delnevo | Assignee: | Trung Luu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 2d 5h | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| 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 20, Add-Ons 21 |
| Story Points: | 5 |
| Description |
|
When a request comes to Mgnl from the public, we should decide which content to serve. This decision depends on whether a test is running on the requested node. This can be done in the filter chain to intercept the request and serve the right content.
AC
Flow:
|