Boards, backlog and views
Grid vs list, drag-and-drop columns, backlog grooming and the calendar.
Boards, backlog and views
Tasks — grid and list
The same dataset rendered two ways. The toolbar toggle switches between a dense grid and a row-per-task list; both apply the same server-side filters (status, priority, assignee, sprint, search) and both open the same create/edit dialog. Choose grid when you are scanning, list when you are reading descriptions.
Kanban — drag and drop
Columns map to the task statuses. Dragging a card between columns sends PUT /api/tasks/<id> with the new status; a card that is one day's occurrence of a schedule sends PATCH /api/task-instances/<id> instead. Cards open to a detail panel that edits the same task row. The day picker above the columns chooses which day the board draws, and a day that has not arrived is read-only.
Backlog — grooming
Everything without a sprint. From here you estimate story points, set priority, assign an owner and pull items into a sprint. This is the page to use before a planning session, and the page the AI Scrum Master reads when it drafts a plan.
Calendar — dates
Sprint boundaries, task due dates and calendar events in one month view. Events are full CRUD through /api/calendar/events and /api/calendar/events/<id>. The Google Calendar integration card produces an internal feed URL only — it does not sync with Google in this build.
Choosing a view
- Planning a sprint: backlog, then the AI Scrum Master draft.
- Running the day: kanban.
- Auditing or bulk-editing: tasks in list view, then POST /api/tasks/bulk.
- Communicating dates: calendar.
View state is yours
Filters, view mode and column order are part of your persisted settings, so a page comes back the way you left it. Resetting them is a card in /dashboard/settings.