-
Task
-
Resolution: Done
-
Major
-
None
-
None
We need a way to test notification messages in production for specific organizations without turning on the feature flag globally.
Right now, the plan was to use the Insights QA user in production to validate that notifications are being sent correctly. However, we've hit a blocker: enabling the feature flag to start sending messages to the notifications service would affect all users. Even if a user hasn't configured themselves to receive these notifications, the deduplication logic kicks in and prevents the messages from being delivered later when the feature is fully rolled out. This means we can't safely flip the flag just for testing purposes.
The proposal is to introduce a new feature flag that holds an allowlist of organization IDs. This feature flag would be configurable via app-interface. When an org ID is present in this allowlist, notification messages would be sent for that organization regardless of whether the global feature flag is enabled or disabled. This decouples testing from the global rollout and lets us validate the full notification flow in production without any side effects for other users.
Acceptance Criteria
- Implement the feature and ensure the notification gets sent even when the feature flag is disabled if the organization is in the new property
- Update test plan and implement it as a component tests
- Update app-interface to allowlist the Insights QA user in production
- blocks
-
SWATCH-4584 Enable feature flag swatch.swatch-notifications.send-notifications
-
- Backlog
-
- mentioned on