Details
-
Bug
-
Resolution: Fixed
-
High
-
6.7.12, 7.2.11, 7.13.2, 7.6.12, 8.5.4, 8.13.3, 8.20.3
-
6.07
-
132
-
Severity 2 - Major
-
176
-
-
Description
NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.
Summary
View on board call (GHGoToBoard.jspa) iterates over all boards the user performing the lookup has access to and executes them one by one to check if given issue belongs to it. So by design View on board performance will degrade with increasing numbers of boards. This is also multiplied by the complexity of each Board's JQL.
Steps to Reproduce
- Create Jira with many issues (> 500k)
- Create many boards (> 1000)
- Go to View on board link at any issue.
Expected Results
Call executed within 1 minute. It's JScript timeout.
Actual Results
Call times out with Communications breakdown error. If you open the link in a new tab it might take 200 secs.
Note on fix
A new "Find on Board" functionality had been introduced.
We’ve replaced the old way of viewing issues on boards with an entirely new experience aimed at improving the responsiveness of searching for boards that display a particular issue.
Now, instead of searching through every board in the system, Jira will only search the boards that make explicit mention of an issue’s project key and the boards you viewed recently. This way, you’ll get more meaningful results much quicker than before.
What has changed:
- We are not searching through all of boards that user has access to
- Search is limited to:
- Boards that make explicit mention of an issue’s project key (project-centric);
- Recently viewed boards;
- Maximum amount of 100 boards;
Workaround
- Increase AJAX calls timeout
- See https://confluence.atlassian.com/jirakb/how-to-change-the-default-ajax-timeout-in-jira-824345485.html
- This will work only for middle-sized instances. Suggested new timeout value: 120 secs
- If possible, reduce the number of boards and their complexity:
- Check scrum boards. Check the sprint dates for the current/last sprint. If a project is inactive then it is highly likely that sprints have not been planned in the recent few months.
- Check kanban board. Run the created/resolved chart for the filter/project in that Kanban board and see. Again, if the project is inactive then not many new issues would had been created in recent past.
- Check empty JQL board.
- The list of JQL filters associated with all Boards can be retrieved running the below query:
select rv."ID", rv."NAME", sr.reqcontent from searchrequest sr, "AO_60DB71_RAPIDVIEW" rv where rv."SAVED_FILTER_ID" = sr.id;
- Disable the View on board functionality:
- Block calls to /secure/GHGoToBoard.jspa at proxy level
- please see example for Apache Httpd:
RewriteEngine On RewriteRule ^/secure/GHGoToBoard.jspa - [F]
- for nginx
# Blocked GHGoToBoard because of severe performance impact. Links # are not supposed to be accessible but people seem to keep find them. location = /secure/GHGoToBoard.jspa { error_page 403 /403-page-disabled.html; return 403; }
Attachments
Issue Links
- is related to
-
-
- Closed
-
-
-
- Gathering Impact
-
- relates to
-
-
- Gathering Impact
-
-
PS-50228 Loading...
-
- Mentioned in
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-