-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
Component/s: Operations - Services
-
None
-
1
-
Severity 3 - Minor
Issue Summary
In Opsgenie, customers could create "External Services" linked to Public Statuspages.
While these continue to work in JSM, they are very hard to identify. This is because:
- The Service does not show the Statuspage it is connected to
- The Alerts created by these do not link back to the Service in Assets
Steps to Reproduce
- Create an External Service in Opsgenie and migrate to JSM
- Add an incident to the Statuspage page that is connected
- Notice the Alert does not help connect to the Service
- And notice that the Service does not show which Statuspage its connected to, nor which components on those pages were selected
Expected Results
For Services to be linked to the Alert.
Actual Results
A name shows in the Alert - but it can be very hard to find the actual Service it links to.
Workaround
Currently, there is no known workaround for this behaviour. A workaround will be added here when available