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.

​
Context

Task Detail and Project Detail include a compact Context section for authorized Atoll-owned Artifacts and external references. Artifacts are structured documents such as research, decisions, plans, and release checklists. The Context section loads Artifact metadata first; content loads only when you open an Artifact. Open an Artifact to read its current sanitized revision, view immutable revision history, or use its direct link. Editors and admins with write access can create an Artifact, revise its title or content, link an existing Artifact to the current task or project, and unlink it. Read-only members can view authorized Artifacts but do not see these mutation controls. Revision saves use the current revision as a concurrency check, so a stale editor must reload before saving.

​
External references

Task Detail and Project Detail also include authorized external references. Link a supported GitHub pull request by pasting its URL. Atoll resolves the provider identity server-side before it stores the reference; the URL you enter is not treated as the reference identity. Each canonical reference shows its object type, authority location, provider provenance, last-observed freshness, and whether it is currently resolvable. The external-reference list is an index only. It does not load pull-request content. Editors and admins can unlink a canonical reference when they have write access to its task or project. Existing task PR links remain visible in the Pull requests section with a Legacy label during the compatibility period. The section is hidden when empty. These records are read-only in the Context view and are not canonical External References. They do not provide provider identity or provenance for the canonical reference model. 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. Board Settings also lets project editors and admins classify each column for future start-work recommendations: Candidate (may be started), Active (already started), or Excluded (do not recommend). New projects use Backlog = Excluded, Todo = Candidate, In Progress = Active, and Done = Excluded. Existing columns remain unconfigured until an editor saves a role. An unconfigured column is not eligible for future recommendation consumers, and a project with no Candidate column shows a Board Settings warning before that configuration can be used for start-work recommendations. The system cancelled status is always excluded and is not configured as a column role.

​
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; archived and cancelled blockers are satisfied. Archiving preserves the dependency edge and release point. Restoring the blocker re-evaluates that same point and can block the dependent again. Configurable release points and cancelled-blocker behavior are unchanged. New dependencies default to the blocking project’s Done column, and the dependency release point can be changed from the task dependency panel. When you create a task, use Add blocked by or Add blocking in the Dependencies section to search for and attach existing tasks. Select the release point for each blocker when the project has custom board columns. If a dependency link fails after the task is created, Atoll keeps the new task, continues its other post-create work, and shows which dependency link needs attention. 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.