Closed Bug 1625240 Opened 5 years ago Closed 11 months ago

Different actions should be able to register different enrollment/exclusion logic

Categories

(Firefox :: Nimbus Desktop Client, enhancement, P2)

Product:
Firefox
Component:
Nimbus Desktop Client
Type:
enhancement

Tracking

()

Status:
RESOLVED WONTFIX
Tracking Flags:
Tracking Status
firefox76 --- affected

People

(Reporter: k88hudson, Unassigned)

References

Details

Right now obviously this just applies to messaging so it's not a big deal, but if we want to expand the scope of a unified experiment module we would need to handle different enrollment/exclusion logic for each action

Iteration: --- → 76.2 - Mar 23 - Apr 5
status-firefox76: --- → affected
Priority: -- → P2
Iteration: 76.2 - Mar 23 - Apr 5 → 77.1 - Apr 6 - Apr 19
Iteration: 77.1 - Apr 6 - Apr 19 → 77.2 - Apr 20 - May 3
Iteration: 77.2 - Apr 20 - May 3 → ---
Severity: normal → S3

This is no longer relevant

Status: NEW → RESOLVED
Closed: 11 months ago
Component: Messaging System → Nimbus Desktop Client
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.