Current behavior
The list view (both in the browser UI and via backlog task list --sort) only supports sorting by id or priority. The milestone card/board view correctly respects task ordinals, but the list table does not expose ordinal as a sort field.
Desired behavior
Add ordinal as a sort option in the list view, both in the browser UI (as a sortable column header) and via the CLI (--sort ordinal). This would allow users who prefer the information density of the list view to see tasks in their manually assigned sequence rather than defaulting to ID order.
Use case
When using ordinals to define a deliberate build sequence within a milestone (e.g., wave-based ordering for a large phase), the list view is the most practical way to scan status across all tasks — but it shows them in ID order, which loses the sequencing signal entirely. The board view preserves ordinals but is less scannable for status checking.
Version
1.45.1
Current behavior
The list view (both in the browser UI and via
backlog task list --sort) only supports sorting byidorpriority. The milestone card/board view correctly respects task ordinals, but the list table does not expose ordinal as a sort field.Desired behavior
Add
ordinalas a sort option in the list view, both in the browser UI (as a sortable column header) and via the CLI (--sort ordinal). This would allow users who prefer the information density of the list view to see tasks in their manually assigned sequence rather than defaulting to ID order.Use case
When using ordinals to define a deliberate build sequence within a milestone (e.g., wave-based ordering for a large phase), the list view is the most practical way to scan status across all tasks — but it shows them in ID order, which loses the sequencing signal entirely. The board view preserves ordinals but is less scannable for status checking.
Version
1.45.1