Guide
Custom sorting is available for most data Views:
In addition, it works in the same way in Relation Filters and Sorts.
Choosing a sort order only affects how the entities are shown in the specific view - it does not change anything about the entities themselves. Sorting can be applied in many places, and an entity doesn't 'know' where it sits in the sorting order for any given view.
For this reason, it is not possible to make calculations based on the position of an entity in a view, e.g. you cannot create a formula which calculates a running sum of number values. Nor can you use a formula to get an entity's position in a list.
You can do these kinds of calculations in a Report view however, since reports operate on databases, not individual entities.
Default sorting
When no custom sorting is specified, the items are ordered manually via drag'n'drop (aka by Rank):
As soon as any custom sort is enabled, the drag'n'drop reordering stops working.
Add custom sorting
To order items by a certain Field, add a sort:
One can't sort by collections: many-to-many relations, multi-select Fields, and Assignees.
While sorting by a relation Field uses Name of related Entities, sorting by select values (incl. State) uses the values' Rank (aka manual prioritisation).
Use multiple sorts
In case multiple sorts are applied, every next sort serves as a tie-breaker for the previous ones.
In the example above:
Features are sorted by state
Features with the same state are sorted by RICE score
To change the order in which sorts are applied, drag'n'drop them.
Sort per DB (+ columns and rows)
When cards of multiple DBs are present on the same Board, List, or Feed View, you can specify custom sorting for each DB independently:
In this case, all Entities will be first sorted by DB and then by each DBs custom sorting.
In the example above:
Dev Tasks go first sorted by State and Feature
Bugs come next sorted by Urgent
Features come last sorted by Release
In a similar way, you can specify custom sorting for rows and columns.