Product
Every planning surface reads the Atlas backlog.
Lists, boards, sprints, releases, roadmap, and calendar are views — not copies. Custom fields, statuses, priorities, and assignees travel with the task.
Hierarchy
Three nested levels. The fourth is rejected.
Root tasks indent at 0. Subtasks add one level. A subtask of a subtask of a subtask is the last allowed depth. Nest validates create and reparent so a move cannot bury a subtree past the limit.
The list also shows status, priority, owner, due date, and progress — the same fields the board card uses.
Execution
Swimlanes and statuses on the same cards.
Filter Atlas 2.4 by Platform, Payments, or Docs. Cards keep keys (ATL-176), Git PRs, comment counts, and remaining progress. Filter is decorative comprehension — the product enforces the same grouping in the live workspace.
Schedule
Roadmap, sprint, release, and calendar share dates.
The 10-week grid from 23 Feb through late April 2026 places access policy, QA train, webhook retries, schema freeze, docs, and the 27 Mar cutover. Today is marked on 11 Mar. Those bars are the tasks you already saw on the board.
Month view
The same cutover appears on the calendar.
March 2026 holds Sprint 18 (2–13 Mar), today on the schema freeze, Sprint 19, and the 27 Mar cutover. Those dates are the roadmap bars — not a second plan kept in a slide.
Configuration
Statuses, priorities, and custom fields stay on the record.
Projects define statuses (Ready, In progress, Review, Resolved) and priorities. Custom fields — risk, environment, owning department, customer-facing, Git URL — sit beside assignees and dates. Knowledge articles live next to the work.
Collaboration
Comments, mentions, and a knowledge base on the item.
QA can mention frontend on Safari 18. A schema freeze comment can link PR #866. Mentions and knowledge articles stay in the project; they are not a side chat that loses the task id.
Capacity
Workload against a 32-hour sprint week.
Nora, James, and Samir show allocated hours versus capacity for Sprint 18. Over-allocation is visible before the cutover week, not after.
See the surfaces in a live workspace.
Get started if your organization allows registration, or sign in to an existing project.