Sorting a view by a single field only answers half the question. Everything sharing the same value stays in whatever order it was already in, so a table sorted by Status returns a block of In Progress items with nothing distinguishing their order inside the block. Which of those items matters most is a question the view cannot answer.

With this update, views support a second sort level. Items sharing the same value on the primary field are ordered by the secondary field, and the secondary field carries its own direction, set independently of the primary. Sort by Status ascending, then by Priority descending, and the In Progress block reads highest priority first.

To add one, open the sorting dropdown on any view and add a secondary sort field.

Hierarchy sorting presents a view as a tree: each item followed by its children, and each of those followed by its own children, level by level. The order within any one level was the hierarchy's own manual order, and it was the only one available. No level could be arranged by what its items say about themselves.

With this update, the secondary sort orders every level of the tree. Sort by Hierarchy, then by Status, and the items at the top level are ordered by status among themselves, so one still in To Do comes before one already In Progress. Each of them is still followed by its own children, and those children are ordered by status among themselves too. The same rule repeats at every level below. The tree structure stays intact, and each layer inside it is ordered by a field.

To use it, select Hierarchy as the primary sort and add a secondary sort field from the same dropdown.