When a user is removed from Opsgenie, their Slack account is not decoupled and fails to connect/disconnect in the future

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • Component/s: Incidents - Slack
    • None
    • 1
    • Severity 2 - Major

      Issue Summary

      Customer reports that they had an incorrect email address in Slack, which was connected to an Opsgenie account with the same Email. The email address was then updated in Slack, and the Opsgenie account with the incorrect email was deleted, and replaced with a new Opsgenie Account using the correct email address. When the user then attempted to use /connect to connect the updated Slack account to "Opsgenie for Incident Management", which matched the new Opsgenie account, they received the error seen in the screenshot

      Steps to Reproduce

      1. Create an Opsgenie account with Email Address 1 and a Slack account with Email Address 1
      2. Use /connect to connect these accounts
      3. Delete Opsgenie account with Email Address 1, and update email on Slack Account to Email Address 2
      4. Create a new Opsgenie account with Email Address 2, and attempt to run /connect to connect to the updated Slack Account with the new Opsgenie Account
      5. Error stating "Sorry, that didn't work. Try Again" appears in the bottom right https://share.getcloudapp.com/5zuPL1X7

      Expected Results

      Running /connect should allow the user to connect their account to the new Opsgenie account, or at least prompt them to disconnect

      Actual Results

      Error above is received

      Workaround

      No workarounds exist currently, user is unable to connect their account to Opsgenie Incident Management

        1. image-2022-12-01-19-02-50-268.png
          152 kB
          Shivam Naik
        2. image-2022-12-01-19-04-17-852.png
          46 kB
          Shivam Naik

            Assignee:
            Piyush Kumar
            Reporter:
            Shivam Naik (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: