Groups, rows and getting work onto a board
A board is a stack of groups, each holding rows. Rows you type in yourself sit alongside rows synced from Jira, GitHub, GitLab or Azure DevOps — in the same groups or their own.
Two groups; the second row is selected for a bulk action.
What it does, and where the data comes from
Every project row lives in a Group, and every group belongs to one board. Groups you create hold the rows you add by hand. When a source is attached, its issues land in their own group per Jira project, GitHub repo, GitLab project, or Azure DevOps project — kept separate so a sync never overwrites a group you're using for manual work.
How to work with groups and rows
- Add a group or row — use the add-row affordance at the bottom of a group, or press
Nwith a row focused to jump straight to it. Keyboard chordGthen↑/↓jumps between groups. - Reorder by drag — grab a row anywhere and drop it at a new position in the same group; the new order is saved immediately, with the board reverting the row if the save fails.
- Move between groups — drag a row across a group boundary to reassign it; a row moved this way keeps its edits and comments.
- Select multiple rows — press
Spaceon a focused row to toggle its selection; selecting one or more rows shows a bulk action bar at the bottom of the screen. - Bulk actions — with rows selected, Change status, Move to group, Duplicate, or Delete the whole selection at once, then Clear the selection.
- Bulk field edits — a selection can also be given a single value for a column, including CapEx/OpEx. This is the fastest way to mark a set of epics as roadmap scope, which is what turns on Team Focus roadmap coverage and classifies everything beneath them.
- Delete a single row — focus it and press
Delete/Backspace(confirms first), or use the row's own delete control.
Under the hood
A bulk edit is one request for the whole selection rather than one per row, so changing fifty rows costs the same round trip as changing one — and fires the same automations a single-row edit would.
Every drag, delete, and bulk edit applies to the board instantly and rolls back only if the server call fails — so the board never waits on a network round trip to feel responsive. A row that fails to save briefly flashes red instead of silently reverting.
If it looks wrong
| Symptom | Cause | Fix |
|---|---|---|
| A dragged row snaps back | The move was rejected by the server (e.g. stale board state) | Refresh the board and retry the drag |
| Deleted row reappears | The delete request failed | Check your connection and delete again — it flashes red on failure |
| Can't add or delete rows | You hold Viewer, not Editor, on this board — row writes are enforced server-side | Ask a board Owner for Editor access; see Owners, sharing and who can see a board for what each role controls |
Related
- System fields vs the columns you add — what each column in a row shows.
- Filtering, sorting and finding rows — narrow down a busy board.
- Owners, sharing and who can see a board — what board roles control today, and what they don't.
- Connecting sources — how synced groups get onto a board.
Last updated