Uploaded image for project: 'Opsgenie'
  1. Opsgenie
  2. OPSGENIE-496

As a customer I would like to set channels to private by default in the Slack incident management app

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • Incidents - Slack
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      User goal

      With the help of private channels, customers can exclude specific incidents from all users.

      Suggestion

      Finding a way to set the Slack app to create a private channel vs a public channel in Slack with the incident management tool.

      Workaround

      Currently, there is no workaround to share

            [OPSGENIE-496] As a customer I would like to set channels to private by default in the Slack incident management app

            > This is a must to use Opsgenie for Security Incidents.

            Agree 337990d1fa59 - I'm considering pulling us off of OpsGenie less than a year after onboarding it due to this reason. Its clear this product isn't receiving even small quality of life updates, let alone basic features like this.

            John McCall added a comment - > This is a must to use Opsgenie for Security Incidents. Agree 337990d1fa59 - I'm considering pulling us off of OpsGenie less than a year after onboarding it due to this reason. Its clear this product isn't receiving even small quality of life updates, let alone basic features like this.

            This is a must to use Opsgenie for Security Incidents.

            Due to the fact that Security Incidents can be caused by Malicious Insiders, the public channel just notifies the attacker of the fact that his actions are being investigated, which beats the whole purpose.

            We opted out of Opsgenie for Incident Management due to this reason. Same stands for Incident Management flows created through Jira (Also no ability to create Private Channels).

            Dmitriy Alekseev added a comment - This is a must to use Opsgenie for Security Incidents. Due to the fact that Security Incidents can be caused by Malicious Insiders, the public channel just notifies the attacker of the fact that his actions are being investigated, which beats the whole purpose. We opted out of Opsgenie for Incident Management due to this reason. Same stands for Incident Management flows created through Jira (Also no ability to create Private Channels).

            John McCall added a comment - - edited

            This should be a very easy feature to add, and a big win for any company that has to regularly deal with sensitive client information. It would allow us to utilize OpsGenie Incidents better and prevent us from having to consider other tools.

            John McCall added a comment - - edited This should be a very easy feature to add, and a big win for any company that has to regularly deal with sensitive client information. It would allow us to utilize OpsGenie Incidents better and prevent us from having to consider other tools.

            Same here where our company disabled the creation of public slack channels.  Without OpsGenie adding this feature, we cannot use the Slack integration.

            Peter Soncek added a comment - Same here where our company disabled the creation of public slack channels.  Without OpsGenie adding this feature, we cannot use the Slack integration.

            In addition to the reason mentioned above, our company disables creation of public Slack channels by non-admins (includes the integration) for accidental information disclosure concerns.  For both of these reasons, we need the integration to create private channels.

            Franklin Rizzoto added a comment - In addition to the reason mentioned above, our company disables creation of public Slack channels by non-admins (includes the integration) for accidental information disclosure concerns.  For both of these reasons, we need the integration to create private channels.

            We are also interested in this feature. We have a requirement that all incident discussions are to be private and members/responders need to be invited as they are needed.

            Lucas Arnström added a comment - We are also interested in this feature. We have a requirement that all incident discussions are to be private and members/responders need to be invited as they are needed.

              ac923919ac6b Himanshi Gaba
              eergun@atlassian.com Emirhan
              Votes:
              28 Vote for this issue
              Watchers:
              20 Start watching this issue

                Created:
                Updated: