-
Suggestion
-
Resolution: Fixed
-
None
-
1
-
2
-
Issue Summary
The JSM Operations alert page does not show the Entity Field.
It is visible in the Opsgenie UI and all of our API responses.
If the field is available in the API, then we need show it on the JSM Operations alert page as well.
Steps to Reproduce
Generate an Alert on JSM Operations, and verify the entity field is part of the payload from the Incoming data:
{"alertLogOwner":"Jira","actionOwner":"Jira","alertId":"67b29501-3ec0-4896-96e4-9815cc5bae0a-1726776906564","_incomingData":{"syncName":"same site","_parsedData":{"-teams":["06d3401c-05fd-4b0a-aa05-d6b654c57995"],"-actions":[],"-tags":["Escalated_L2","deletetix"],"description":"what comes in now?","alias":"ITSAMPLE-139","_details":{"issueKey":"ITSAMPLE-139","priority":"Medium","status":"On Hold"},"source":"jira-service-management-cloud","message":"check entity using something else","priority":"P2","entity":"ITSAMPLE-139"},"syncType":"jira-service-management-cloud","syncId":"7748f626-b43b-4463-8edc-175e9fda2f1c"},"alertLogType":"system"}
Go to the generated Alert and look for the Entity field.
Expected Results
The Entity field should be visible on the Alert and populated with the relevant data.
Actual Results
Entity Field is nowhere to be found.
Checking the Alert from the REST API shows that the entity field is present in the Alert's data:
"values" : [ { "acknowledged" : false, "actions" : [], "alias" : "ITSAMPLE-139", "count" : 1, "createdAt" : "2024-09-19T20:15:06.564Z", "entity" : "ITSAMPLE-139", "id" : "67b29501-3ec0-4896-96e4-9815cc5bae0a-1726776906564",
Workaround
It may be possible to extract the Entity field using an extra property as outlined here: https://jira.atlassian.com/browse/JSDCLOUD-14561. However, some customers have reported inconsistent results with this method.
- relates to
-
JSDCLOUD-14561 Ability to display the Entity field in the alert view by default
- Closed
- links to
- mentioned in
-
Page Loading...