-
Bug
-
Resolution: Unresolved
-
Low (View bug fix roadmap)
-
None
-
9.12.11
-
9.12
-
1
-
Severity 3 - Minor
-
Issue Summary
When a user conducts a search for issues that includes the parent link in the output, the performance of the page is negatively impacted. The execution of the identical JQL search requires more than 10x the standard duration to generate the output.This issue also affects gadgets and dashboards due to the rendering of the Parent Link field. The impact is exacerbated when the number of projects and issue types is substantial.
This is reproducible on Data Center: yes
Steps to Reproduce
- Create a large instance containing over 8,000 projects.
- Establish a significant number of issue types within this instance.
- Configure the JPO hierarchy for the issue types.
- Define the parent-child relationships among a considerable number of issues.
- Execute a JQL search that returns a substantial number of records.
- Conduct the search without including the parent link as a column in the output.
- Perform the search again after incorporating the parent link as a column in the output.
Expected Results
The page should load within the same timeframe or with a little variance, regardless of the additional column included in the output.
Actual Results
When the parent link column is included in the output, the performance of rendering the page decreases significantly.
You can check for the timing for <BASEURL>/issues/?jql=<JQL> in har without parentlink. vs <BASEURL>/rest/issueNav/1/issueTable in har with parentlink for comparison.
216ms vs 2-3 sec
The variation in time is contingent upon the data and the node infrastructure.
Workaround
Currently, there is no available workaround. To mitigate performance issues, it is advisable to remove the parent link from the output. Additionally, it is recommended to adhere to the guidelines outlined in Guardrails for the Jira environment, as the rendering time is influenced by the number of projects and issue types present in the environment.
- links to
