BoardLaneBy
What the task board splits its rows – its lanes – by: nothing, the assignee, the category, or the phase (top-level summary task) each piece of work belongs to.
public enum BoardLaneBy
Remarks
A lane is a value of a task field, as a column is a value of ProjectTask.Status,
so dropping a card in another lane sets that field. Tasks with no value share a lane of their own,
placed last.
See also
Members at a glance
| Members | |
|---|---|
Assignee | One lane per ProjectTask.Assignee, in the order the assignees first appear,
with unassigned work last. Dropping a card in a lane assigns the task to that person. |
Category | One lane per ProjectTask.Category, in the order the categories first appear,
with uncategorised work last. Dropping a card in a lane sets the task's category. |
None | One lane: the board is just columns. |
Parent | One lane per top-level summary task – a phase of the plan – in plan order, with work outside
any phase last. Dropping a card in a lane makes the task a direct subtask of that phase, by setting
its ProjectTask.ParentId. |
Members
Assignee
One lane per ProjectTask.Assignee, in the order the assignees first appear,
with unassigned work last. Dropping a card in a lane assigns the task to that person.
Category
One lane per ProjectTask.Category, in the order the categories first appear,
with uncategorised work last. Dropping a card in a lane sets the task's category.
None
One lane: the board is just columns.
Parent
One lane per top-level summary task – a phase of the plan – in plan order, with work outside
any phase last. Dropping a card in a lane makes the task a direct subtask of that phase, by setting
its ProjectTask.ParentId.