-
Bug
-
Resolution: Fixed
-
Low
-
8
-
Severity 2 - Major
-
-
Warranty
Issue Summary
Currently, when a user adds a new Mobile App contact method the new contact method does NOT automatically get added to the user's "New Alert" notification rule; whereas if the user were to add a new email or Voice contact methods, the new contact method will automatically get added to the user's "New Alert" notification rule.
Steps to Reproduce
- Log into Opsgenie via the Web UI to delete the Mobile app contact method being tested, if they already exist. This should delete the contact method from the New Alert notification rule and other notification rules.
- To add the new Mobile app, log into Opsgenie via the Opsgenie mobile app. Refresh the Notification tab to observe the result in the New Alert notification rule.
- To add the new SMS contact method, add it via the Web UI, key in the verification code from the phone when prompted. Refresh the Notification tab to observe the result in the New Alert notification rule.
- To add the Email or Voice Contact method like in steps 3. Refresh the Notification tab to observe the result in the New Alert notification rule.
Expected Results
Expecting the new Mobile app contact method to be added to the user's New Alert notification rule just like when adding the new email or Voice contact method.
Actual Results
The new Mobile app contact method did not get added to the user's New Alert notification rule; whereas the new email or Voice contact method gets added into the user's New Alert notification rule.
Workaround
The workaround would be for the user adding the new contact method to check their Notification tab to manually add the new contact method to their "New Alert" notification rule and any other notification rules where desired. It is also advisable to delete any unused or old contact methods, like the old Mobile app contact method(s) when switching to a new phone or phone number.
- mentioned in
-
Page Loading...