I'm using jira software, but I think it's getting slower because there's a lot of content on the Khanban board. Please check if it is right to slow down if there are more tickets on the original Khanban board.
Hello @이상미
Thank you for reaching out.
Can you please confirm if the board you are using is a Next-gen or Classic?
In fact, performance issues are very hard to troubleshoot without having a closer look in the background logs of the application, however, we were able to identify some common backlog lacks that usually causes some slowness:
If you are using a Next-gen Kanban board, I believe you might be facing the following bug:
Performance degradation of Next-gen boards with more than 300 cards during initial load
We are internally discussing this bug and checking how we can properly workaround it.
Now, if you are using a Classic Kanban board, I believe you might be facing one of the bugs below:
Slow loading Agile boards in IE11
Loading boards in Firefox is slower compared to Chrome
In that case, can you try to use Chrome and completely clear your browser cache to check if you get a better performance?
Additionally, feel free to vote and watch the bugs to increase its priority and also receive notifications about any updates.
If the scenarios above are not applied to you, please let us know.
Yes, the board you are using is a next-generation project.
It seems to be getting slower as the number of tickets increases, but when can the bug be improved ??
It will be upgraded to standard, but if loading loading of tickets is slow, it will be difficult to purchase.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @이상미
Thank you for confirming you are using Next-gen.
Unfortunately, we don't have any alternative workaround for now. In fact, performance issues require a detailed analysis of data and behavior in the background which can take some time, so we are currently working to get it fixed as soon as possible.
For now, the best we can suggest you would be to write a comment to our developers directly in the bug reported, so they can take a closer look at your specific case and may provide some details that can help.
I have also added this question in an internal comment of the bug, so our developers can have more details about the impact this bug is causing to our customers.
Let us know if you have any questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.