Boards & sprints
TaskFlow gives you a board to visualise work in progress, a backlog to prioritise upcoming work, sprints to plan iterations, and a calendar to see what's due when. These views show data for the active project, so pick a project first.
Boards
A board shows all of a project's issues as cards arranged in columns by workflow status (for example To Do → In Progress → Done). Use it to see what's in flight and spot bottlenecks; iteration planning lives on the backlog and sprint pages.
Move a card to a new column to change the issue's status — the board respects the allowed transitions in your workflow (on a touch screen, use the card's "Move to…" menu instead of dragging). Open a card to jump to the full issue detail page.
WIP limits
A kanban column can carry a work-in-progress limit — the number of issues that column should hold at once. When a column goes over its limit the board tells you, which is usually the first visible sign that work is piling up in one stage instead of flowing through.
The limit is a signal, not a barrier: you can still move a card into a full column. The point is to make the queue visible so the team decides what to do about it, rather than having the tool block someone mid-task.
Backlog
The backlog is the list of issues that aren't yet in a sprint. Use it to:
- Groom upcoming work — move issues into a sprint and back, refine summaries and estimates.
- Decide what goes into the next sprint.
- Keep long-term items visible without cluttering the board.
Sprints
A sprint is a time-boxed set of issues your team commits to for an iteration.
Typical flow:
- Create a sprint and give it a name and a goal (and dates, if you plan them).
- Fill it from the backlog — move the issues you'll work on into the sprint.
- Start the sprint — it becomes active, and its contents show as a separate section on the backlog page.
- Work the board — move cards across as work progresses.
- Close the sprint — it gets the completed status. Move unfinished issues yourself beforehand: drag them into the next sprint or back to the backlog before closing.
Sprint activity feeds the Velocity and Burndown reports — see Reports & analytics.
Calendar
With the calendar feature enabled, the Calendar page lays the project's issues out on a month grid by their due date — a quick read on what's landing this week and where the crunch is. Colour tells you the state at a glance: done, in progress, not started, overdue.
Drag an issue to another day to reschedule it — that changes its due date (on a computer; on a phone the calendar is shown as a list, and due dates are changed on the issue itself). Issues with no due date don't appear on the calendar — set the date on the issue page.
Roadmap
For the longer horizon, the roadmap shows epics and their contents on a timeline. See Reports & analytics → Roadmap.
Choosing between kanban and scrum
- Use kanban for continuous flow — support, operations, or teams without fixed iterations. WIP limits matter most here.
- Use scrum with sprints for planned iterations with a committed scope.
You can adapt as your team's process evolves; workflows, boards and sprints are all configurable.
Where to go next
- Issues & tasks — everything on an individual issue.
- Reports & analytics — velocity, burndown and more.
- Project configuration — set up workflows (administrators).