Drag and drop
Boards are direct manipulation surfaces: drag tickets within a column, between columns, into and out of the backlog, and drag whole columns to reorder them. Changes land for everyone watching the board in real time.
What you can drag
- A ticket within its column — reorder it against its neighbors.
- A ticket to another column — drop it exactly where it should sit in the destination column. This is also how status changes: the column a ticket sits in is its status.
- A ticket into or out of the backlog — the backlog is a drag target like any column.
- A column — drag a column header to reorder columns on the board.
- A multi-selection — select several tickets (press
Xon each, or⌘ + A/Ctrl + Afor all in a column), then drag any selected ticket to move the whole group. The group lands in order at the exact drop position, written as one atomic change — either every ticket moves or none do.
While you drag
The card you pick up tilts slightly, grows a little as if lifted off the board, and follows the pointer, and a dashed outline marks where it will land: between two tickets in whichever column you are over, starting at the card's own place. The column you dragged it out of closes up. Release and the ticket lands exactly where the outline was. To put it back, press Escape.
When you drag a multi-selection, the card in your hand shows how many others are coming with it (+2), and the whole group lands at the outline.
A board wider than the window fills the screen, and each column scrolls its own tickets. Hold a card (or a column) near the left or right edge of the board and the board scrolls sideways to the columns out of view; near the top or bottom of a column, that column scrolls. To get around without dragging anything, use the scrollbar along the bottom of the board, turn the mouse wheel over a column header or the space between columns, or press on empty board and drag it sideways. Moving the keyboard focus to a column that is out of view scrolls it into view.
Drags are optimistic: the board updates the moment you drop, then confirms against the server. If the write fails (for example you lost connection), the board rolls back and shows a toast.
Keyboard alternative
Every drag has a keyboard equivalent. Focus a ticket with J / K or the arrow keys, then press Space to pick it up: ↑ / ↓ move the outline one place up or down, ← / → carry it to the neighboring column at the same position, Space drops it and Escape puts it back. Or press S to move it to a different column or the backlog. For several tickets, select with X first — S then moves the whole selection. See Keyboard shortcuts for the full list.
Move to top or bottom
To send tickets to the top or bottom of their column without dragging past everything in between, click a ticket's key to select it (click more keys to add to the selection), then pick Move to top or Move to bottom from the menu beside it. Several selected tickets move as one block and keep their order. From the keyboard, ⌘ + Shift + ↑ / Ctrl + Shift + ↑ moves the selection, or the focused ticket when nothing is selected, to the top; ↓ instead of ↑ moves it to the bottom. ⌘ + ↑ / Ctrl + ↑ and ⌘ + ↓ / Ctrl + ↓ move the focused ticket one place at a time.
To work the menu itself from the keyboard, press . while tickets are selected: ↑ / ↓ walk its rows, → or Enter opens Move, Tags or Assignee, ← or Escape closes that submenu, and a second Escape clears the selection. Tab (or . again) hands focus back to the board and keeps the selection.
Both work in the backlog too. In a column you have sorted by anything other than Priority (created, updated or time in column), they are switched off: they change the priority order, which that sort does not show, so the cards would not visibly move. Switch the column back to Priority to reorder it.
From an agent or the API
AI agents and scripts reorder tickets too, through reorder_tickets on the hosted MCP server or POST .../tickets:reorder on the REST API: to the top or bottom of a column, or right before or after another ticket, for one ticket or several at once, optionally moving them to another column in the same call. Several tickets land as one block, in the order given. The board updates live for everyone watching, as it does for a drag. A reorder within a column is not recorded in ticket history; a move to another column is.
Like Move to top, this changes the priority order. If you have sorted the column by created, updated or time in column, the cards stay where that sort puts them; switch the column back to Priority to see the new order.
How ordering works
Can stores each ticket's position as a rank string (a lexorank), not a numeric index. When you drop a ticket between two others, it gets a new rank string that sorts between its neighbors — no other ticket needs to change.
This matters for two reasons:
- Realtime safety — two people reordering the same column at the same time cannot corrupt each other's ordering; each move touches only the moved ticket.
- No renumbering — a board with thousands of tickets reorders just as fast as a board with ten, because moving one ticket is always a single-document write.
You never see rank strings in the UI; they exist so that ordering is stable, fast, and conflict-free.