View grouping

This page lists the fields a view can split its tasks by, and how each view type shows the groups. The steps are in Filter, sort and group a view.

Groupable fields

The Group by button in the view header opens a menu with these fields, in this order. None comes first where a view type allows it. In a GTD view, GTD queue is separated from the other fields in the menu.

Field	One group for each	Tasks with no value go to	Offered	Used in
GTD queue	Up next, Put off, Closed	—	in GTD views only	Run a GTD session
Stage	Not started, Active, Done	—	always	Set up a list
Status	status	No status	always	Set up a list
Priority	None, Low, Normal, High, Urgent	None	when the Priority feature is on	Create and edit tasks
Assignee	member	Unassigned	when the Assignee feature is on	Assign and watch tasks
List	list	—	always	Organize folders and lists
Story points	value	No estimate	when the Story Points feature is on	Estimate with Scrum Poker

You can't group by Tags: filter by them instead.

Fields that need a list feature

The three feature-gated fields (the Offered column above) follow the list features of the lists the view draws from:

• A view over lists offers the field when at least one of its lists has the feature on.
• A view over a whole workspace or folder offers all three.

Grouping by view type

Each view type keeps its own grouping, except GTD and Scrum Poker, which use the List's. Switching type shows that type's grouping.

View type	How groups show	None offered	Starts grouped by
List	a header over each group; Collapse group folds it	yes	nothing
Table	a section for each group, which folds the same way	yes	nothing
Timeline	rows gathered under each group's label, at the left	yes	nothing
Kanban	a column for each group	no	Status on a list's own board; Stage on every other board, even one over a single list
GTD	a header over each group, as in List	no	GTD queue
Scrum Poker	a header over each group before Start session, as in List	yes	the List's grouping (nothing on a new view)

GTD, Scrum Poker and List share one grouping. Group the List by Priority and the GTD and Scrum Poker views group by Priority too. GTD queue chosen in the GTD view shows as no grouping in the List and in Scrum Poker.

Scrum Poker

When	Group by button	Groups
before Start session, for a member who can start a session	shown	as in List
before Start session, for a member who can't, or on a personal view	shown	none; the screen shows No estimation session yet, and a pick changes the grouping of the view's List (and GTD)
once Start session has opened the Task Queue	hidden	the queue and the session stay flat, in the grouped order

Views without groups

View type	Group by button	Effect
Calendar	shown	the grouping is saved but doesn't split the calendar
Dashboard	shown	a pick isn't kept; the button stays at Group by
Feed, Dashboard V2	hidden	—
Relations	hidden on a view of its own; shown on a list's own page	the graph ignores grouping
a running GTD session	hidden	—
any type, on a list's own page with Read access	hidden	—

Grouping rules

• Groups come first in the order. The view sorts by the group field first; your sort orders the tasks inside each group. Group by Priority and sort by Due date: the groups run from None to Urgent, and inside each group the earliest due date is on top.
• A change saves at once, with no Save button, for everyone who opens the view.

Edit access needed

To change a shared view's grouping you need Edit access to the view and a permission set that can update views, such as List/Folder manager or Admin. On a list's own page the button is hidden without Edit access. Personal views are always yours to change.

Dropping into a group

In a grouped List, or across the columns of a Kanban board, dragging a task into another group changes the task:

Grouped by	Dropping into a group…
Stage	sets the first status of that stage in the task's list
Status	sets that status
Priority	sets that priority
Assignee	assigns that member; Unassigned clears the assignee
Story points	sets that value; No estimate clears it
List	moves the task to that list; a subtask stays put, so move its parent instead
GTD queue	changes nothing

If you lack permission to change the field or move the task into the target list, the task stays and a message explains why:

• <field> can’t be changed for tasks in this list, where <field> is the grouped field, or Status when you drop into a Stage group;
• You can’t move tasks into this list.

Group button labels

Header shows	Meaning
the grid icon alone, gray; Group by as its tip	the view is not grouped
the grid icon alone, green; Group by List as its tip	grouped, in the narrowest header
Group · List	grouped by List; the tip reads Group by List
· List	the same, in a narrower header
Tools → Group	a narrow window folds the header's tools into one menu