Skip to main content
Projects hold execution work. Tasks are the units that move across board and list views.

Optional Product groups

Use Products in workspace navigation to find optional groups of projects and strategy. Owners and admins can create a Product, edit its name and description, and archive or restore it from its overview. Products use stable ID-based links, so renaming one keeps its link intact. Projects keep their own boards, permissions, tasks, and history. The sidebar groups readable projects under their Product and still opens each board directly. Projects without a Product stay under Standalone. Workspaces with no Products keep their existing project navigation and need no extra setup. Use the arrow beside a Product or Standalone to collapse or expand its projects. Select the Product name to open its overview. To attach, reassign, or detach a project, open its Project Settings, choose a Product or None / standalone, then select Save Product. Organization owners and admins can change affiliation for active and already-archived projects. This does not change task states, project archive state, or workflow columns. Other authorized viewers can read the Product label on the project overview. Product archive retains ownership and links. It does not archive projects or issues; active children remain in the sidebar under the archived Product. Restore the Product before editing its profile or assigning new work into it. There is no Product Delete action. The Product overview shows readable projects, Product-owned goals, KPIs and initiatives, linked context, and a Product-scoped preview of canonical operations. An Organization-owned goal linked to a Product KPI stays Organization-owned. Execution assignments stay separate from actual current executions. Source errors stay visible, and these recent previews are not totals or health scores. Product visibility grants no additional project, strategy, agent, or attention permissions. See strategy owners and the existing Product API.

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. On the full task page, Back returns to the view where you opened the task, with its filters and scroll position. If you open a task directly, in a new tab, or from an external page, Back to board opens that task’s project board. For a task with no project, Back to projects opens the workspace project list. 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. Choose Artifact source when you create or edit a document to select an External Reference already in that Context. Keep the current source, select a replacement, or choose No source. Each save creates a revision with its own source snapshot. Open revision history to inspect earlier sources. If the live reference is removed, the snapshot remains and shows No longer linked in Context. Source links are visible only to readers who can access the recorded source issue or project. Atoll does not copy or synchronize external content. 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 have one Add reference action in Context. Choose Web link for an HTTPS URL or GitHub pull request for a verified provider reference. GitHub mode resolves immutable provider identity before saving. A failed verification does not create a manual link. Web links appear in Documents with Added manually and Content not verified. Atoll does not load, embed, verify, or sync the page. URLs with credentials are not accepted. The Added date belongs to this task or project link; it is not a provider observation or a freshness guarantee. Query strings and fragments are preserved. Adding the same normalized URL again reuses the link. Provider references retain their provenance, observation freshness, and resolvability. View-only users can read references. Editors can add and unlink references when they have write access to the task or project. Unlinking one target does not remove the reference from other targets. Legacy task PR links remain readable with a Legacy label. Context has no separate Add PR action and does not migrate or remove those older records. 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. Scheduled intervals can be at most 10,000. Completion mode keeps its existing interval range. By default, when a recurring task is marked Done, Atoll creates the next instance and advances its due date according to the recurrence settings. To create occurrences while the current task remains open, set Create next task to On schedule, then choose a local time and IANA timezone. The maintenance sweep creates one occurrence at a time and preserves the schedule across daylight-saving changes. The root task owns the schedule; each generated task remains in the same recurrence chain. In scheduled mode, an archived root or disabled schedule is skipped, and a transient failure remains recoverable for a later sweep. Completing a scheduled occurrence does not create another task. During a daylight-saving overlap, Atoll uses the earlier instant. A nonexistent local time moves forward by the size of the gap. The schedule controls when tasks appear. Due dates continue separately from the root’s due date using the existing date recurrence. For example, a weekly task can appear on Monday and remain due on Friday. The root’s due date stays unchanged. Editing its due date resets future deadline progression without changing the appearance clock. Changing the appearance time or timezone preserves the calendar cadence and deadline progression. Selected weekly days also apply to the due-date cadence. Monthly creation keeps the original day of the month and uses the last day in shorter months. If task creation is denied, its target is missing, or its saved inputs are invalid, that scheduled occurrence is recorded as failed and is not retried. Correct the access or settings for future occurrences. Temporary failures and uncertain creation results remain recoverable on a later sweep. Once a chain has entered scheduled mode, recurrence edits on a generated task update the root, even after a switch back to completion mode. Such chains follow the root’s current mode. A disabled root in such a chain or an inaccessible root does not create a successor. Other task edits stay on the generated task. Send root recurrence changes separately from other task edits. You must have write access to the root to change its schedule. Deleting the root leaves scheduled-mode generated tasks as ordinary tasks; they do not become schedule owners. Completion-mode tasks retain their existing recurrence behavior after root deletion. Legacy completion chains keep and edit each occurrence’s settings locally until a deliberate series-root move or root preference action establishes root ownership. Switching one to scheduled mode adopts that occurrence’s cadence on the root. Switching modes preserves selected weekdays. Weekday arrays and weekly completion in completion mode remain temporarily unavailable; null can still clear selected weekdays. For CLI usage, see Issues, comments, and projects.

Choose where new tasks start

Use New tasks start in in the recurrence controls. Choose a nonterminal column from the task’s project. The project default is Todo when present, or the first nonterminal column. Changing this setting preserves the current task’s status and scheduled appearance time. Root-owned occurrences edit the series setting; local task edits remain separate. When you move a recurring series to another project, historic occurrences stay where they are. The next task uses the series’ current project and selected column, including when you complete an older occurrence. This also applies to legacy completion series after an explicit move or root setting change. Completing a scheduled occurrence does not create a task immediately. Board Settings shows recurring target references before column deletion. Select a nonterminal replacement for these targets, independently of the replacement for current task statuses and dependency release points. The changes commit together. If access or a replacement is invalid, the column remains.

Archive before delete

Archive projects or tasks for reversible removal from active work. Project archive also excludes its tasks without changing their individual archive flags or workflow columns. Archived projects are read-only; restore the project before editing or restoring a task in it. Use the Projects Archived view and an active project’s Archived Tasks view to find retained work. See Archive and restore work for permissions, restore capacity checks, task markers, and dependency behavior. Permanent delete is restricted to owners/admins and should be used sparingly.

Vercel deployment evidence

With a Vercel connection, project Context shows preview, staging, and production deployment state, revision, provider time, and observation freshness. Task Context includes a deployment only when one task’s linked PR has the exact same numeric repository ID and SHA in that project. Old deployed revisions stay project-only when they do not match. Production supersession follows the latest authenticated production target, including rollbacks; preview/staging ready ordering stays within its own environment. Missing revision proof is shown as unavailable. Deployment ready does not complete a task or prove Production Testing or human acceptance. Unlink removes only that association; a later verified update can restore it.

Browse compact Context groups

Context groups evidence under Development, Design, Discussion, Documents, Deployments, and Production. Each group starts with at most five items. Choose Show more within that group, or Refresh Context to start again. Design and Discussion stay empty until their adapters are available. Open a document to load its body and revision details. Choose Show delivery details to load check and workflow details. Creating or editing a document loads its source choices only when the editor opens; Link existing loads Artifact candidates only when requested. Direct document links still work when the document is outside the first page. Each item preserves its authority and freshness. A failed source leaves other groups available. External observations become stale after 24 hours. Use the About Context evidence help control with a pointer, keyboard, or touch for the evidence distinction. A ready deployment does not establish human acceptance.

Earliest agent start

Set Earliest agent start on a task to prevent a new Atoll runner start before that calendar date. The date uses the workspace time zone, shown beside the field. Workspace owners and admins can change the IANA time zone in Settings → General; existing workspaces default to UTC. A time zone change changes future eligibility on the next read or claim. Use due date copies the current due date once. Later due-date edits do not change the saved earliest start. You can save a date later than the deadline; the form shows a warning. Clear the field to remove the restriction. Planning, assignment, human work, current-work inspection, existing runner leases, exact claim replay and attention recovery continue. On or after the date, the normal access, dependency and workflow checks still apply. A new recurring occurrence starts without this date unless explicitly supplied. The gate controls Atoll runner lease admission. It does not prevent direct execution records or external harnesses that do not claim Atoll runner leases.

Sub-issues

Open a task and use Sub-issues → Attach existing to link another full task. The list shows each child’s issue number, title, status, and assignee, with a done/total count. Select a child to open it. Use its Parent link to return, or Detach on the parent list to remove the link. You need edit access to the child and its old and new parents. Children may belong to another project in the same organization. Only one hierarchy level is allowed. Deleting or archiving a parent keeps and detaches its children. The checklist remains separate, and child progress does not change parent status.

Plan sub-issues on the board

Parent cards show done/total progress. Child cards show a Parent link. Counts include all readable, active children, including other projects and children outside the current board filters. Each child’s project Done-stage columns determine completion. Archived children do not count. Use More filters → Hide sub-issues to focus on parent deliverables. Remove Sub-issues hidden to show the children again. This view choice is stored in the board URL and does not change the issues or parent counts. In the create form, use Select parent to choose an optional parent. From a parent task, use Sub-issues → Add sub-issue to prefill the parent, project, and milestone. You can change the project before you create the child. To attach several existing tasks, select their board cards with Ctrl-click (Windows/Linux) or Command-click (macOS), then use Set parent. Each task is saved separately with the existing edit and hierarchy checks. If an attachment fails, successful changes remain saved and failed tasks remain selected. Check the error before you try again. The server rejects self-parenting, a second hierarchy level, cross-organization links, and unauthorized changes. For full child issues, parent progress and explicit close/reopen decisions, see sub-issues.