Plan today's work
Open Daily recap before the day starts or before standup. It is your personal view of current work: completed tasks, active initiatives, bugs or synced issues assigned to you, pull requests that need attention, calendar events, blockers, and personal todos.
Use the Board tab when you need a Kanban view of your assigned work across teams: initiatives, synced issues, pull requests that need attention, and personal todos.
Start in Daily recap
Daily recap is not the team board. It answers the personal standup questions first: what changed, what you plan to work on, and what needs help.
| Column | What it contains | Why it matters |
|---|---|---|
| Worked on | Completed tasks from connected apps, agent work, finished initiatives or bugs, and manually added completed work. | Use it to verify what will be reported as done. |
| Planned | Initiatives, bugs or synced issues assigned to you, pull requests you opened, are assigned to, or need to review, calendar events, and todos. | Use it to decide what is actually on your plate today. |
| Blockers | Blocked initiatives, bugs, synced issues, pull requests, or todos. | Use it to make dependencies, missing input, and decisions visible before standup. |
Use the add action when something is missing. Worked on creates a completed task. Planned and Blockers create work with the matching status. The Board tab in the Daily recap header switches to your personal Kanban view.
Personal daily snapshot
Worked on
Completed signals from today
Planned
Ready to start or continue
Blockers
Needs help before progress
Check planning views
Daily recap is for the day. Use the Roadmap for initiatives and ongoing work that should stay visible beyond today. Use the Backlog for ideas, bugs, and feature requests that are not scheduled yet. Use Triage when incoming bugs or feature requests need an accept, decline, or reviewer decision.
Use Boards when you need a Kanban view across people and statuses. Use Ownership when work is missing a clear owner, assignee, reviewer, or escalation path.
Update ownership and blockers
Before standup, make sure work has an owner, assignee, and current status. Add a team only when the work should appear in a specific team view.
Move blocked work to Blocked and add the reason in the description or comments. Include who can help or what dependency is holding it back so the blocker appears clearly in recaps, standups, and team views. Use Blockers when you need to review or route blocked work across a team.
If the work belongs to a larger planned effort, create or update an initiative before sharing the update.