Lattice Grid

Kanban ยท console.warn

a card move did not persist through the boun...

Printed by Kanban, prefixed [lattice], since 1.127.0.

Warnings reference › kanban:move-writeback:*

Identifier
kanban:move-writeback:*
Raised by
Kanban
Since
1.127.0

What happened

A grid-bound card move wrote the grouping column through grid.edit.setCells and the grid wrote no cells at all, so the card snapped back to its source column. The * in the id is the grid column id the move wrote through, and the message names that column and the setting to change: a column that does not resolve to a grid column, a column that is not writable under the current permissions, a column that is not editable (edit: true on the column, or the grid-level edit switch), or - when the column is editable and writable - a write refused for another reason. The board also shows a visible refusal notice on the board.

The fix

Make the bound grouping column editable and writable: declare the column on the grid, give it edit: true (or edit: { enabled: true }), or grant write permission to it. A board over a read-only grid should be given readonly so the drop is refused before the write is attempted.

The smallest fix

columns: [{ id: 'status', edit: true }]

Reference

Covered in full at the API reference.