-
Bug
-
Resolution: Done
-
Low
-
None
-
Severity 3 - Minor
-
Issue Summary
(yes)
Steps to Reproduce
- Exactly following the slack Integration. https://support.atlassian.com/opsgenie/docs/integrate-opsgenie-with-slack-app/
Expected Results
The "bug" in the documentation is that it is not clear to a user's understanding that enabling an option, let's say "Add Tags" will allow users to add tags to the OpsGenie alert directly from the Slack notification, either by using a Slack button or the "/genie add tag" command. However, if the "Add Tags" is disabled in the Alert Actions section, nobody should be able to add tags to the alert directly from Slack.
The clear explanation that should be in the documentation is that:
"Alert Actions section in the Slack integration configuration determines which alert actions will be sent from Opsgenie to Slack, not the other way around. When an option, such as "add tags," is enabled, a Slack message will be sent when tags are added to an alert."
Actual Results
Incorrect functionality of Alert Actions section in Slack integration configuration and lack of explanation in the official documentation
...
Workaround
Incorrect functionality of Alert Actions section in Slack integration configuration and lack of explanation in the official documentation.
"Alert Actions section in the Slack integration configuration determines which alert actions will be sent from Opsgenie to Slack, not the other way around. When an option, such as "add tags," is enabled, a Slack message will be sent when tags are added to an alert."
Reference OGSP-102655
The content of this bug will be carried on through https://schwarzytest.atlassian.net/servicedesk/customer/portal/31/JCCB-401?created=true
I have requested the documentation to be made clear in a different/corrected channel and that is why I am closing this bug.