-
Bug
-
Resolution: Fixed
-
Medium (View bug fix roadmap)
-
6.4.12, 7.3.5, 7.6.4, 7.6.7, 7.13.0
-
None
-
6.04
-
43
-
Severity 2 - Major
-
67
-
NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.
Summary
Jira 6.4 instance is responding slowly in many screens, with some screens showing timeouts.
Environment
Large instance with many swimlanes or card colours configured for the Agile Kanban board
Expected Results
It works with acceptable performance (20-30 sec).
Actual Results
It works slow (> 30 sec).
Notes
Cause
Cause is boards with many swimlanes and card colours.
For every card colour or swimlane that is defined using JQL, the entire board query is run again, with the additional JQL appended. So if no swimlanes or card colours are defined and the board opens in N seconds, each swimlane or card colour defined is guaranteed to increase the load time by at least another N seconds. Given 5 swimlanes + 2 card colours + the actual board query, this board will take at least 8*N seconds to open.
2 Problems:
- For the customer's instance: "N" is large (lucene is not performant)
- We're running a lot of queries each time we display the board.
Workaround
Remove swimlanes or card colours from the configuration.
Please check KB article: Kanban board loading is slow - performance problems
- causes
-
JSWSERVER-13797 As an JIRA Administrator I want to show to users JQL complexity of the Kanban boards
- Future Consideration
- duplicates
-
-
- Closed
-
- is duplicated by
-
-
- Gathering Impact
-
- is related to
-
- Closed
- relates to
-
-
- Closed
-
-
- Closed
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-13211] Slow Kanban response and performance after upgrade to Jira 6.4
Every once in a while, a query simply has to be extremely complex to show all the issues that you want on the board. The query we're working with now takes about 15s in the issue navigator to execute. However, if that query is used for a Kanban board with no quick filters or swimlanes, the board times out.
We really need to be able to make the board continue to load data even if it takes a long time, whether that's because of swimlanes, card colors, or simply the complexity of the query.
Hi team!
Is it possible to set rule for Kanban boards,
e.g. If number of card color or quick filters, and some rules for main filter like LIMIT parameters.
Cheers,
Gonchik Tsymzhitov
Boards are a central part of Jira. We have thousands, and as admins have no way of managing how many JQL items user/s place in Agile boards. The fact that this can not only have an adverse affect on Jira as a whole, but also can increase the time to load the board is troubling. This is not congruent with the spirit of Jira and how you want your customers to use this tool. Please escalate this. We will be following up with our TAM on this until it is fixed.
We are facing this issue in 7.6.4.
In our Kanban board we are using around 10 swimlanes and filter query "project = ABC AND NOT status changed to closed before -14d".
No card colors were used.
If there is any way to please increase the performance of the Scrum Board also when CARD COLORS JQL Queries are used this would be extremely beneficial.
We are using Jira version 7.6.
We notice on Scrum Boards that if Card Color queries are used then the Scrum Board display performance time is noticeably affected and boards load noticeably slower. This is worse in projects where there are a lot of issues in the backlog, of course.
Example: We have fairly simple JQL queries in the Card Colors section of the scrum board. There are about 10 different colors/queries identified. Thank you.
Is there a plan to fix this issue? We've found this bug is causing heavy disk usage affecting the overall performance of JIRA as threads are blocked waiting on the disk.
Terrell Teague
added a comment - We've switched to a Kanban board and the slowness makes it a big pain.
Terrell Teague
added a comment - We've switched to a Kanban board and the slowness makes it a big pain. We are facing this issue now. Our version is 7.3.6. It's slowing JIRA to almost a halt. Reboot clears the issue but it's not a solution.
Atlassian, does this bug appear in new versions too?
I know it was a year ago, but I agree with Mike. This issue tanks the entire system and should be escalated.
It is unacceptable that JIRA re-runs the search query with the additional queries tacked on. It should run the query once, and then apply color and swimlane data on the returned dataset. Or better yet, turn the color and swimlane queries into columns returned by the underlying SELECT statement.
We’ve invested in improving Kanban performance in a number of ways in several 7.x and 8.x versions of Jira Server and Data Center.
Starting from 7.9 Jira Kanban boards got much faster as they no longer display all unreleased issues.
In Jira 7.12 we have turned off calculation of days spent by each issue in the current column. This was an expensive operation significantly contributing to slowdowns. From 7.12 it has to be manually enabled so only the boards that need this functionality will have it enabled.
In 8.0 all boards and backlogs got a significant performance boost thanks to end-to-end rework.
And from 8.1 colours are lazy loaded and no longer delay the loading of boards.
Additionally from 8.1 boards list from side panel is not longer blocking the rendering of the board making shortening the time to wait.
We believe these changes addressed the majority of performance problems of Kanban boards and we are closing this issue as done. If you are still facing performance issues please let us know in the comments below or create a separate issue. When describing your case please mind that the more details you provide the easier it will be for us to address your issue.