Projects hold execution work. Tasks are the units that move across board and list views.
Project profile settings
Project admins can update a project’s display name from project settings. Use the name for clear navigation and reporting. To change the sidebar emoji or project color, click the project icon in the sidebar and choose from the searchable picker.
Changing a project name updates the visible label without changing the underlying task history. If your team or agents rely on stable project IDs, keep using IDs in API and automation flows.
Task fields
Tasks can include:
- Title and Markdown description
- Status
- Priority
- One or more assignees
- Project, team, milestone, and labels
- Start date and due date
- Dependencies
- Subtasks
- Attachments
- Recurrence
Task detail views
Open a task from the board, list, or full task page to review and update its
details. The task detail modal and full page both expose the task URL copy
action, so you can share the current task without leaving the view you are
working in.
Task detail also shows who created the task. Use creator and assignee context
together when you need to understand who opened the work, who owns the next
step, and who should be notified before closing or changing direction.
Strategy links
Projects and tasks can connect execution back to Strategy.
Project overview shows linked initiatives when the project is explicitly tied
to an initiative or when project tasks are linked to initiatives. Issue detail
shows initiative chips for strategic work, and task creation can include an
initial initiative link. When the right initiative does not exist yet, create it
inline from the task modal and Atoll selects it for the new task.
Use strategy links when a task exists to move a KPI or deliver an initiative.
Leave routine operational work unlinked unless it truly affects a strategic
objective.
Statuses
Default statuses are:
| Status | Meaning |
|---|
backlog | Not ready for active work |
todo | Ready to pick up |
in_progress | Actively being worked |
done | Completed |
cancelled | Closed without completion |
Projects can define custom board columns. The API accepts the project’s configured status values, and cancelled is always valid.
The current CLI validates --status against the default set: backlog, todo, in_progress, done, and cancelled. Use the API for custom project statuses until CLI support is added.
Priorities
| Value | Label |
|---|
0 | Urgent |
1 | High |
2 | Medium |
3 | Low |
Assignees
Tasks support multiple assignees. Use one assignee when ownership is clear. Use multiple assignees for collaborative work where all participants need notifications and visibility.
Dependencies
Dependencies express blocking relationships. A task can be blocked by another task or can block another task.
Use dependencies when task order matters:
Design approval -> Landing page implementation -> Launch announcement
Atoll rejects circular dependencies and duplicate dependency links.
Recurring tasks
Recurring tasks can repeat daily, weekly, biweekly, monthly, or on a custom day interval. You can set or change recurrence from the task detail modal or the full task page.
When a recurring task is marked done, Atoll creates the next instance and advances its date-only dueDate from the completed task’s due date. If the task has no due date, Atoll starts from the current local date. Date-only recurrence math is timezone-safe, so a due date like 2026-05-11 stays anchored to that calendar day instead of shifting across UTC boundaries.
Archive before delete
Archive tasks when you want reversible removal from active lists.
Permanent delete is restricted to owners/admins and should be used sparingly.
atoll issue archive ATOLL-42
atoll issue unarchive ATOLL-42