-
Bug
-
Resolution: Fixed
-
Low
-
7.2.2
-
None
-
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
- 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.
Component/s | Original: A4J DoS [ 61319 ] | |
Component/s | New: Rule execution (engine) [ 60805 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Closed [ 6 ] |
Status | Original: Needs Triage [ 10030 ] | New: In Progress [ 3 ] |
Fix Version/s | New: 7.2.3 [ 92830 ] |
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 |
Fix available in A4J 7.2.3