-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
1
-
Severity 3 - Minor
-
Issue Summary
This is reproducible on Data Center: Yes
Slack notifications display "System" instead of a username when an alert is unacknowledged via the Slack button.
Steps to Reproduce
- Follow the instructions in the support link to integrate Slack with Opsgenie.
- Create an alert in Opsgenie to receive notifications in Slack.
- Use the Slack button to acknowledge the alert.
- Unacknowledged alert using the Slack button
Expected Results
When unacknowledge an alert using the Slack button, the notification message should display the user's username instead of the system's.
Actual Results
When the Unacknowledged button in a Slack channel is clicked, the action person is always "System," but when the Acknowledge button is pushed, the username of the user who clicked the button is shown.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
Unacknowledge an alert by pressing the Slack button, which shows "system" as the action person rather than the actual username.
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
1
-
Severity 3 - Minor
-
Issue Summary
This is reproducible on Data Center: Yes
Slack notifications display "System" instead of a username when an alert is unacknowledged via the Slack button.
Steps to Reproduce
- Follow the instructions in the support link to integrate Slack with Opsgenie.
- Create an alert in Opsgenie to receive notifications in Slack.
- Use the Slack button to acknowledge the alert.
- Unacknowledged alert using the Slack button
Expected Results
When unacknowledge an alert using the Slack button, the notification message should display the user's username instead of the system's.
Actual Results
When the Unacknowledged button in a Slack channel is clicked, the action person is always "System," but when the Acknowledge button is pushed, the username of the user who clicked the button is shown.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available