Skip to main content
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. 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: Projects can define custom board columns from Board settings. The API also accepts a project’s configured status values, and cancelled is always valid. For CLI usage, see Issues, comments, and projects.

​
Priorities

​
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:
Atoll rejects circular dependencies and duplicate dependency links. Dependency references are clickable, including references to tasks in another project. Projectless dependencies remain visible but unlinked. Inaccessible targets are not exposed. The blocking task must belong to a project because its release point is a board column in that project. A projectless task may be the blocked target. Each dependency has a persistent release point in the blocking project’s ordered columns. A blocker satisfies the dependency when its current column reaches that point; cancelled blockers are satisfied. New dependencies default to the blocking project’s Done column, and the dependency release point can be changed from the task dependency panel. Existing dependencies are backfilled to the blocking project’s done column when the release-point migration runs. During a rolling deployment, an older dependency row may omit release fields; treat that row as the legacy open-blocker behavior until the migration is applied. If a blocker moves to another project, Atoll asks for an explicit destination release column for every dependency before it commits the move. Board Settings also shows separate issue and release-reference counts before a column is deleted, and requires independent destinations when either count is non-zero.

​
Recurring tasks

Recurring tasks can repeat daily, weekly, biweekly, monthly, or on a custom day interval. When a recurring task is marked Done, Atoll creates the next instance and advances its due date according to the recurrence settings. For CLI usage, see Issues, comments, and projects.

​
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.