-
Sub-task
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
None
-
1
-
False
-
-
False
-
subs-swatch-lightning
-
-
-
Lightning NEXT
PO Summary:
By adopting a default behavior group, we are reducing the notification setup from two steps to one so that customers can more easily monitor their usage and avoid unexpected overage costs.
Notifications team offers the ability of setting up a default "Behavior group" for our notification.
This would mean that we could reduce the opt-in from a 2 step process (1. create behavior group, 2. click the check-box to turn on the notification) to a 1 step process where by default they would only have to click the checkbox.
In this thread will be discussed the adoption of this capability: https://redhat-internal.slack.com/archives/C09BCH0GRT7/p1772031181738159
Acceptance Criteria:
- Verify that the default behavior group has been created for Org ID 11789772 (credentials can be found in the vault, link is in the Release document)
- That can be checked here https://console.redhat.com/settings/notifications/configure-events?bundle=subscription-services&tab=behaviorGroups
- We expect to see a behavior group with the decided name (https://issues.redhat.com/browse/HCCDOC-4672) and the lock icon, meaning it is not possible to modify that.
- blocks
-
SWATCH-4606 Provide a demo about SWATCH notifications for ProdOps
-
- New
-
- relates to
-
RHCLOUD-45452 Create a default behavior group for Subscriptions Usage
-
- New
-