Boards and backlogs

A board shows records as cards in columns, one per state, to see at a glance where each one stands and move them by dragging. A backlog shows them as a tree, with what each record holds underneath, like a project with its tasks.

Both need a form that saves the records first. A backlog can be added when the application is created; a board, from Edit application, once the entity has states.

Entity settings

Under Entities, in the application editor, each entity has its settings:

Field that names a record: the field used as each record's name on boards, trees and lists. If you don't pick one, it's the first text field, or the first folio when there's no text.
States: the steps a record goes through, in order, like "New", "In progress" and "Solved". A new record starts at the first. Each state has a category (Proposed, In progress, Resolved, Completed or Removed) that says what it means, whatever it's called. A state that has records can't be removed.
Child records: which entities can go under a record of this one, like tasks under a project.
On each record: whether it allows Comments and Links to other records. Both start off.

Board

Each board column gathers one or more states, and each state goes in only one column, so every card has a single place.

Drag and drop: drop a card on another column to change its state. If the entity has transitions, it only moves along them; if the change isn't allowed, the card goes back.
New: each column has its button to add a record that starts there.
Swimlanes: columns can be split into rows, one per parent record, per option of a select field, or per record of a relation, plus a row for what has none. Dropping a card on another row changes its parent or gives it that value. Each row can be collapsed.
Cards: clicking a card opens its record in the form.
Show more: each column shows its first 50 cards, oldest first, and the number next to its name counts them all. If it has more, Show 50 more brings the next ones.

Backlog

The backlog lists the top records and, under each, the ones it holds with their state. + New adds a top record, and each record offers to add children.

Group by gathers records under a heading per option of a select field or per record of a relation, plus one for those with none. Each heading can be folded.

The backlog shows the first 50 top records, with everything under them, and Show more brings the next ones. If there are more than 500 records of one entity on one level under them, a notice says not all of them are shown.

Inside a record

Opening a record, under its data shows what its entity allows, in tabs with a count:

State and parent: to move it to another state (with a button per transition, if the entity has them) or put it under another record.
Links: to connect it with another record of the application as "Related to", "Blocks" or "Comes before". From the other record it reads the other way round: "Blocked by" or "Comes after". "Comes before" fits, say, a task that can't start until another one finishes.
Referenced by: the records whose relation fields point to this one, with a button to add another.
Comments: who wrote what, and when.

The history keeps every change of value, state and parent.