Hi, thanks for taking the time to report this and for the clear steps to reproduce.
That really helps.
The issue your reported is actually working as intended, and I’m happy to explain why.
The “Unassigned” column is an admin-only working lane. It stays visible for admins
and editors even when it’s empty, on purpose, so you can drag items into it at any
time or use it as a simple backlog for ideas you haven’t slotted into a status yet.
If we hid it when empty, there’d be nowhere to drop items to un-assign them, which
would take away a handy part of the workflow.
For regular visitors, the column already behaves the way you’d expect. It only shows
up when it actually contains one or more unassigned items, and it stays hidden
otherwise. So your public board never displays an empty Unassigned column.
Since you’re seeing it while logged in with editing access, that’s exactly why it’s
showing for you.
One thing we’re considering, based on your feedback, is adding a small “drop items
here” hint inside the column when it’s empty, so it reads clearly as an intentional
drop zone rather than looking like leftover space. If we ship that, it’ll be
admin-only too.
Thanks again for the sharp eye. Please keep the reports coming.
Thanks for the detailed explanation. That makes sense now, especially the drag-and-drop workflow for admins. I initially assumed it was a UI issue because the empty column looked like leftover space rather than an intentional drop zone.
I like the idea of adding a small “Drop items here” placeholder or similar visual hint when the column is empty. I think that would make its purpose much clearer for editors and help avoid the same confusion in the future.
Thanks again for the clarification and for considering the improvement.