Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-15368

Deleted site still listed in the "Select a site" option in Assist MS Teams and Slack

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • JSM Chat
    • None

      Issue Summary

      When a site that had a connection with Assist in MS Teams or Slack is deleted, for example, a Sandbox site, the site will still be listed in the "Select a site" option in Assist. However, the customer may not be able to remove the connection because the site has already been deleted.

      This is reproducible on Data Center: (yes) / (no)

      Steps to Reproduce

      1. Create a sandbox site.
      2. Open a JSM project, and configure chat with MS Teams or Slack
      3. Confirm the connection is successfully connected.
      4. Try to create ticket via Assist , if MS Teams or Slack connected to multiple site , it will show in the "Select a site" list
      5. Then, delete the sandbox site.
      6. Open Assist to create a ticket

      Expected Results

      The deleted site was removed from the "Select a site" list

      Actual Results

      Deleted sites still exist in the list.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            [JSDCLOUD-15368] Deleted site still listed in the "Select a site" option in Assist MS Teams and Slack

            The issue is fixed.
            Disconnected or permanently deleted sites won't show up in Select a site prompt

            Rajat Sharma added a comment - The issue is fixed. Disconnected or permanently deleted sites won't show up in Select a site prompt

            This doesn't just affect the "Select a site" option when creating an issue.

            It also results in request types appearing duplicated when you're trying to connect a JSM site to a channel because the request types are pulled from both production and sandbox. We've had to add "Sandbox" to the names of request types on sandbox so we know which ones to select in the configuration.

            This is a real hindrance to setting Assist up.

            Chris Garstin added a comment - This doesn't just affect the "Select a site" option when creating an issue. It also results in request types appearing duplicated when you're trying to connect a JSM site to a channel because the request types are pulled from both production and sandbox. We've had to add "Sandbox" to the names of request types on sandbox so we know which ones to select in the configuration. This is a real hindrance to setting Assist up.

              Unassigned Unassigned
              nroslan Atiqah Roslan
              Affected customers:
              2 This affects my team
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: