Boards & sprints
Kanban, Scrum, list, calendar, timeline and the sprint lifecycle.
Each board is a workspace. Tabs adapt to the board type: Kanban boards show [List][Kanban][Calendar][Timeline], and Scrum boards additionally show [Backlog][Sprint].
Views
- Kanban: drag-and-drop columns; the header warns when a WIP limit is exceeded
- Backlog: prioritize and bulk-edit items to pull into a sprint
- Sprint: track work in the active sprint across status columns
- List: a sortable table view with customizable columns
- Calendar: see tasks on a monthly calendar by due date
- Timeline: a Gantt-like view of epics/stories across date ranges




Set up a new board from an existing board’s settings
When creating a board, choose "Take settings from another board" and pick one: that board’s way of working is set up on the new board. You configure your team’s setup once instead of rebuilding it for every new board.
- Copied: the workflow (columns, colors, WIP limits, transitions and their role requirements), custom fields, issue types and roles
- Task templates come along by default; members do not. Both are checkboxes: carrying members over would silently grant board access
- Not copied: tasks, sprints, versions, comments and the GitLab connection
- The new board gets its own short code, so task numbers never get mixed up
- If the source is a docs space, its page templates and roles are copied
Sprint lifecycle
- 1Create a sprint (planned state) with a goal and start/end dates.
- 2Move tasks from the backlog into the sprint and check capacity.
- 3Start the sprint. A board can have only one active sprint at a time.
- 4During the sprint, burndown and remaining work update automatically.
- 5Complete the sprint; move unfinished work to backlog, the next sprint, or a chosen sprint.
Inside a task
- Subtasks: split work into parts, and a subtask can have its own subtasks
- Relations: link a task to another task, a document or a diagram (blocks, relates to, duplicates)
- Files: attach images, PDFs, Office documents and archives to the task or a comment - pasting into the comment box works too
- History: every field change is recorded with who and when - the answer to "why is this task waiting"
- Mentions: write @person or @group in a comment and the right people get notified
Capacity, burndown, velocity and average cycle time are computed automatically from sprint data; no extra input needed.