Sprint board slow to update

[Drew Glicker]

Hello all, 

My team is having an issue where our sprint board is too slow to update when ticket details change. Something as simple as a status transition or flagging an issue may take 30 seconds or more before it's reflected on another user's board. This is causing us issue when, for example, we're doing our daily QA and need to see which tickets have been moved from "Ready for QA" to "In QA". Steps to reproduce below:

1. User A and User B open the same sprint board (with no filters)
2. User A transitions ticket 1 from "to-do" to "in progress"
3. User B has the sprint board open. Ticket 1 is still "to-do" on their screen.
4. Sometimes after 30 seconds the board refreshes for user B and ticket 1 accurately shows as "in progress"
5. Sometimes, waiting does nothing and User B needs to manually refresh the board for ticket 1 to update. 

We're using sprints, FWIW. Is this expected behavior? Is there a workaround? Our board isn't very big, typically contains about 30 issues at a given time. We expect it to update in real-time like other "board" products we've used, like Trello. 

Thanks!

[Trudy Claspill]

Hello @Drew Glicker 

Is this a Company Managed project or a Team Managed project?

If it is a Company Managed project, what is the filter for the board?

Do you have a lot of Quick Filters (or Custom Filters) defined?

Are you using Swimlanes (or Group By)? If so, what do you have that set to?

What browser are your users using? Have they tried different browsers?

Do you notice the same slowness when you are prioritizing the backlog?

How many sprints have there been for this board?

If your board is drawing issues from just one project with no other criteria in the filter, how many issues are there in that project?