Issue Summary

      We use “Jira Server” app for MS Teams and Jira integration in our company. The details from our developer: All operations with the app stopped working. If the bot is told to "create", a window with an error "Unable to access the app. Try again." appears. When it worked, it looked like this: a) the response to the bot's commands is delayed for a period of up to several tens of seconds. b) on the "create" command, a window with the "create" button appears, after clicking on which a window for entering the signature should appear. The time before this window appeared was sometimes extended to several minutes. C) when using messaging extensions, the issues list might appear in a few tens of seconds. etc. Since we have a separate server allocated for testing (which is not loaded with anything else), and monitoring confirms that there is no load on this server, we assume that all delays occur on the application side. The details from our tester: I have tried to open chatbot tab assigned to me after the timeout for four-hour. The loading was really long (more than 30 seconds) and the errors appeared in the console while loading. Then the app stopped working with error. 

      Steps to Reproduce

      1. Create issue in Bot 
      2. error "Unable to access the app. Try again." appears or the response to the bot's commands is delayed for a period of up to several tens of seconds

      Expected Results

      Issues are created and loaded in 2-3 seconds

      Actual Results

      Issues either are not created or it takes some time to load it.

      Workaround

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

            [JSWSERVER-21889] Slow performance while creating issues in Bot via MS Teams

            No work has yet been logged on this issue.

              Unassigned Unassigned
              zvorona@atlassian.com Zoryana Vorona (Inactive)
              Affected customers:
              3 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: