Certain issues slow to "activate" swimlanes on Kanban board to transition them

Question

When we drag research tickets or story tickets out of their current lane, you must wait for any other lane to "activate" before you may transition it. Some of these tickets, particularly the story or research (or even bug tickets) must be held out of their current lane for upwards of 4-6 seconds before other lanes are activated to where you may transition the issue to another lane.

Anyone seen this before? We have played with memory and looked at CPU and it doesnt appear to be resource related.

Thanks!

Andrew Stickler · Answer

I have recently started seeing a similar problem with an Scrum board when drag-dropping issues to reorder them or assign to different versions or epics. I don't think it is addin-related (no new addins), but it possibly happened when Chrome updated to V 75.0.3770.100 (64-bit).

I am using Jira Server v8.2.1.

The Chrome developer console shows the messages in the screenshot below.

Andrew

Jack Brickey · Answer

the later. This is certainly not normal behavior and feels like an addon conflict to me. You could also try creating a new board all-together and see if the issue follows. Are other boards exhibiting this? Has it start happening following the addition or upgrade of addon?

Alex Lorsung · Answer

Or shed light on the add-on causing problems...