Uploaded image for project: 'Automation for Jira Server'
  1. Automation for Jira Server
  2. JIRAAUTOSERVER-164

Searches for Insight Objects trigger requests for each letter inserted.

    • Severity 2 - Major

      Issue Summary

      After the release of the 7.2.2 version, there were changes in the way that Automation for Jira interacts with Insight's API. Whenever you try to search for objects, for each letter inserted, Automation for Jira is triggering requests, resulting in an excessive amount of them, causing performance issues for larger data sets.

      Steps to Reproduce

      1. Create rules with Insight components and performing searches for larger data sets.

      Expected Results

      • Searches are triggered with an input delay that reduces the performance impact on the application.

      Actual Results

      • Each letter triggers a number of requests causing performance issues.

      Workaround

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

            [JIRAAUTOSERVER-164] Searches for Insight Objects trigger requests for each letter inserted.

            Andriy Yakovlev [Atlassian] made changes -
            Component/s Original: A4J DoS [ 61319 ]
            Component/s New: Rule execution (engine) [ 60805 ]
            Daniel Ramotowski made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Closed [ 6 ]

            Fix available in A4J 7.2.3

            Daniel Ramotowski added a comment - Fix available in A4J 7.2.3
            Daniel Ramotowski made changes -
            Status Original: Needs Triage [ 10030 ] New: In Progress [ 3 ]
            Daniel Ramotowski made changes -
            Fix Version/s New: 7.2.3 [ 92830 ]

            This issue triggers around 3000 requests within 1-2 seconds in our environment when trying to type the name of an object and therefore hangs the entire browser for quite some until all of the requests fail, probably due to some overload.

            Michael Bachmann added a comment - This issue triggers around 3000 requests within 1-2 seconds in our environment when trying to type the name of an object and therefore hangs the entire browser for quite some until all of the requests fail, probably due to some overload.
            Gregory Peres (Inactive) made changes -
            Description Original: h3. Issue Summary

            After the release of the 7.2.2 version, there were changes in the way that Automation for Jira interacts with Insight's API. Whenever you try to search for objects, for each letter inserted, Automation for Jira is triggering requests, resulting in an excessive amount of them, causing performance issues for larger data sets.

            h3. Steps to Reproduce

             # Create rules with Insight components and performing searches for larger data sets.


            h3. Expected Results

            # Searches are triggered with an input delay that reduces the performance impact on the application.

            h3. Actual Results

            # Each letter triggers a number of requests causing performance issues.

            h3. Workaround

             Currently, there is no known workaround for this behavior. A workaround will be added here when available
            New: h3. Issue Summary

            After the release of the 7.2.2 version, there were changes in the way that Automation for Jira interacts with Insight's API. Whenever you try to search for objects, for each letter inserted, Automation for Jira is triggering requests, resulting in an excessive amount of them, causing performance issues for larger data sets.

            h3. Steps to Reproduce

             # Create rules with Insight components and performing searches for larger data sets.


            h3. Expected Results

            * Searches are triggered with an input delay that reduces the performance impact on the application.

            h3. Actual Results

            * Each letter triggers a number of requests causing performance issues.

            h3. Workaround

             Currently, there is no known workaround for this behavior. A workaround will be added here when available
            Gregory Peres (Inactive) created issue -

              Unassigned Unassigned
              gperes@atlassian.com Gregory Peres (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: