Details
-
Bug
-
Resolution: Fixed
-
Highest
-
79
-
Severity 3 - Minor
-
194
-
Description
Problem
JQL search against an instance with many entity properties and when searching for the entity property results in slow performance and sometimes times out after the 30s time limit.
The problem manifests itself when using the following APIs, either directly or via an app:
Identifying
HOWTO Determine if a JQL query is entity property related
Suggested Solution
Improve the scalability of issue search to cater to such entity property queries.
Why This Is Important
Some add-ons rely on entity properties, and as more customers use these add-ons and their data grows, they may run into issues when running queries against the entity properties.
Notes
When using the Atlassian API, either directly or via an app, the internal timeout currently returns a 500 status code, which is incorrect and does not represent the nature of the problem. This is tracked separately as https://jira.atlassian.com/browse/JRACLOUD-77242.
Workaround
Reduce the search scope to a more specific result set (e.g., with a project in () clause, search against a subset of projects).
Attachments
Issue Links
- is related to
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
HOT-99203 Loading...
-
- causes
-
- links to
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-