Alert Detail Value is not in Alert Analytics after recent update we used to see it
Asked by Albert Alvarez:

![image.png](https://files.slack.com/files-pri/TLAQGDC3Z-F06RJBZLPNG/image.png)![image.png](/t5/image/serverpage/image-id/318464iF35FA6BA5059861F/image-size/large?v=v2&px=999 "image.png")![image (1).png](/t5/image/serverpage/image-id/318465i844383FD5FB0FA92/image-size/large?v=v2&px=999 "image (1).png")


Answers:
author: Tejaswi G
body: Dear Albert,

Thank you for contacting the Opsgenie community. We have noted your request to view alert details in the new Analytics UI.

We have a feature request with the ID [OPSGENIE-1996](https://jira.atlassian.com/browse/OPSGENIE-1996) for this particular request.  
You can upvote the feature request and add yourself to the watcher list to receive updates on the status of the request.

If you have any further queries or concerns, please feel free to reach out to us.

Best regards,  
Tejaswi

comments: author: Albert Alvarez
body: Thank you for the update, Tejaswi. I have a question out of curiosity, as someone working in a similar tech industry. How is it that a feature that was previously available has now become a new feature request? The feature was functionally removed without informing customers and is now causing production issues in our reporting. We are now being asked to vote to have the feature added back, which is frustrating for us. Can you please advise how this issue can be prioritized or escalated? It is causing a bad customer experience on our end.

Regards,

Albert


author: Tejaswi G
body: Hi Albert,

We apologize for the confusion but these changes are part of <https://support.atlassian.com/opsgenie/docs/view-global-and-team-reports/> however, we have an update from our engineering team and the requested feature is now available. This will now allow you to download the detailed alert view.

You can also leave your feedback to our engineering team as a comment to the <https://jira.atlassian.com/browse/OPSGENIE-1996> ticket and If you have any further questions/issues, please feel free to log a ticket with us at:[support.atlassin.com/contact](https://support.atlassin.com/contact) and we are happy to assist you.

Kind Regards,

Tejaswi


author: Basel Qumsiyeh
body: Hi [@Tejaswi G](/t5/user/viewprofilepage/user-id/5145653) this update doesnt solve the problem for us. What we need is the ability to see the "Alert Details" field specifically in reports. This is a custom key/value map that contains metadata that we attach to alerts via the SDK. Specifically, its documented in your SDK [here](https://github.com/opsgenie/opsgenie-python-sdk/blob/master/docs/Alert.md) (see the \`details\` field there).

In the old Analytics UI, we used to be able to see and filter on various "Alert Details" custom fields. In the new Analytics UI, we cannot. We need to be able to export custom "Alert Details" via CSV, and ideally be able to filter on it via the UI.

Thanks


author: Albert Alvarez
body: Hi Tejaswi, Like [@Basel Qumsiyeh](/t5/user/viewprofilepage/user-id/1944681), we need that value exposed on the report as all our reports used it, and the change has broken our previous working functionality.


author: Tejaswi G
body: Thank you for your update and for sharing your feedback on the usage of the Opsgenie Analytics detailed report. I have forwarded your concerns and details to our Engineering team for further review.

Additionally, I encourage you to leave your feedback as a comment on the Feature Request (FR) to ensure it receives the appropriate attention.

Should you have any further questions or require additional assistance, please don't hesitate to reach out to us.


author: Albert Alvarez
body: Hi Tejaswi, I hope this message finds you well. I wanted to express my ongoing concern regarding the recent removal of **production functionality**. It seems that you might be overlooking the potential impact this decision could have on our customers who rely on this feature. Rather than treating it solely as a feature request, it's crucial to recognize it as a significant change that could affect our users' experience.

Is this approach aligned with Atlassian's standard practices? I believe it's essential to handle such changes with careful consideration for their impact on production. Instead of relying solely on customer votes and comments after the fact, especially when dealing with the removal of existing functionality, prioritizing proactive action seems more appropriate.

Today is a report function, but tomorrow, it could be something more critical. Therefore, we must give due attention and priority to addressing these concerns promptly and effectively. Your attention to this matter would be greatly appreciated.

Regards,

Albert


author: Tejaswi G
body: Hi Albert,

Thanks for getting back to us.

I completely understand your requirements and we apologize for any inconvenience it may have caused. I have made sure to communicate your feedback to our Engineering team and the product manager accordingly.

Please feel free to reach out to us <https://support.atlassian.com/contact> for any further queries.

Thank you for your understanding and patience with us.

Kind Regards,

Tejaswi


Tags: cloud