Calendar
Overview
Section titled “Overview”Calendar gives you a time-based view of the same work you see on sprint boards and My Tasks: sprint start and end dates, task due dates, and project milestones laid out across days, weeks, or months.
It is most useful for spotting collisions before they become problems, for example two milestones landing the same week, or a task due date that falls outside its sprint window. Those patterns are much harder to catch from a list or board view alone.
Calendar reads from the same underlying data as sprint planning and tasks, so any date you change on a card or task detail page shows up here automatically; there is nothing separate to maintain.
What you can do here
Section titled “What you can do here”- View sprint dates, task due dates, and milestones on one calendar.
- Switch between day, week, and month views.
- Filter by project to focus on one workstream at a time.
- Spot scheduling conflicts across projects before they cause problems.
- Click through from a calendar entry to its underlying task or sprint.
When to use
Section titled “When to use”- Planning ahead across multiple projects or sprints.
- Checking for date collisions before confirming a new sprint.
- Getting a big-picture view before a stakeholder update.
Prerequisites
Section titled “Prerequisites”- A signed-in member account with product access.
- At least one project with dated sprints or tasks to display.
Where to find it
Section titled “Where to find it”- Sidebar: Calendar
- Direct route:
/calendar
Step-by-step
Section titled “Step-by-step”- Open Calendar (
/calendar). - Choose day, week, or month view depending on the horizon you need.
- Filter by project if you only care about one workstream.
- Scan for collisions, such as overlapping milestones or due dates outside a sprint window.
- Click any entry to jump to its task or sprint detail.
- Adjust dates from the underlying task or sprint if a conflict needs resolving.
What success looks like
Section titled “What success looks like”- You can answer what is due this week across every project without opening each one.
- Date conflicts are caught before they surprise the team mid-sprint.
- Stakeholder updates reference a calendar view instead of manually compiled dates.
Tips & best practices
Section titled “Tips & best practices”- Check Calendar right before confirming a new sprint to catch date conflicts early.
- Use the month view for stakeholder updates and the week view for your own planning.
- Filter by project when the all-projects view feels too noisy.
Common mistakes
Section titled “Common mistakes”- Confirming a sprint without checking Calendar for milestone or due-date collisions.
- Manually tracking dates in a separate document instead of trusting this synced view.
- Forgetting that changing a date here means editing the underlying task or sprint, not the calendar entry directly.