Kanban Board - size issue, constant refresh required, tasks jumping columns

[RT_Ops]

Hi folks, after working with kanban boards for a while now and with a lot of success in managing work across a small team, my team has since expanded to cover 4x the people, and about 20x the tickets. Lucky me

Anyway, work flows into my team as issues and tasks, and I have a kanban board set up dynamically intaking requests of both types and managing them across 12 columns (as I have to separate work by discipline, and my team spans 3 main disciplines). It all works beautifully with tags, assignments...lovely.

However, I have two challenges. The first is the age-old bugbear of tasks jumping between columns on refresh. I know a lot of us in the early days of WF boards got around this by setting all columns to "In Progress" statuses, but even with that, the tickets still occasionally jump the first couple of refreshes after being on the board. Is there any more intelligent way of preventing this as yet?

However my main challenge, I assume due to the sheer size of the board/amount of content on it, is it just crashes on a fairly regular basis. Sometimes I'll get "Response not successful: Received status code 502" when refreshing, sometimes I'll just have the board die and and error message suggesting refreshing it. Does anyone know would this be due to size? Or something else I can actually do something about?

Any guidance, or frankly guesses that are worth a shot, most welcome!

[Doug_Den_Hoed__AtAppStore]

Hi @RT_Ops,

Tagging @KatherineLa, who was the protagonist in a similar script last week, that ended with Happily Ever After.

Regards,

Doug

[KatherineLa]

Thanks, @Doug_Den_Hoed__AtAppStore for the tap-in.

For Board size, I believe the documentation says they cap out around 700 items. My largest one is just under 500 right now. 

Starting with the 502/angry-red-text messages, yes we were plagued by those for awhile until our Boards were almost unusable. I did finally get some network traffic logs from my browser to help the engineering team and as of earlier this week I believe they'd tracked down and resolved whatever pod error was causing the havoc. We've been smooth sailing since then. If you're still seeing the extreme errors, I can write-up how I got the logs they needed to look at what was really happening. This isn't the kind of issue that screenshots of errors can really help with.

As for the jumping columns problem, I finally decided that setting multiple columns to the same status automatically was causing a tug-of-war for control of the cards. It does sort of make sense. If the configuration says "When a card goes into X status, move it here." and multiple columns all reach for it on the same trigger, things are going to get messy. I finally settled on a Completed column that matched Closed/Done and stopped using the status automation for any other columns. I don't have a good suggestion on that one.

Kat