Tasks

Tasks is a workspace planning surface. A Task Space is not an Octonode project: projects own code, workflows, runs, and repository links, while Task Spaces own planning data. One work item can link to several projects, workflows, or pull requests without changing their source.

Tasks requires a hosted workspace with the collaboration capability. Its data belongs to the active workspace and never crosses personal, team, or organization boundaries.

Create a Task Space

Choose a starting template:

• Simple starts with a lightweight To do, Doing, and Done board.
• Kanban adds Backlog, Ready, In progress, Review, and Done statuses.
• Scrum adds backlog and active-sprint planning to the same status model.

Templates seed the space; they are not separate engines. Every space can contain Initiative, Epic, Story, Task, Bug, and Subtask work items. The permanent space key produces stable human references such as OPS-142.

Choose a view

All views are projections of the same work items:

• Board groups cards by status and lets you move work between columns.
• List provides a compact searchable planning view.
• Backlog assigns standard work to future sprints and starts a planned sprint.
• Active sprint shows current sprint work and progress; completing it returns unfinished work to the backlog.
• Calendar places work by due date.
• Timeline shows scheduled work across dates.
• Releases groups work toward a named target date and tracks release progress.

Changing a view never copies a task. Search matches the stable item key or title.

Work item details

Open an item to edit its title, Markdown description, type, status, priority, assignee, parent, dates, tags, sprint, and release where supported. Comments and Activity preserve the discussion and change history. Updates use the current version, so a stale edit conflicts rather than silently overwriting another member's change.

Use the fixed hierarchy: Initiative → Epic → Story, Task, or Bug → Subtask. Sprints apply to standard-level items; subtasks inherit their planning context.

Link engineering context

Attach an Octonode workflow by pasting its Studio URL, or attach a pull request by repository ID and pull number. Links retain identifiers; Tasks does not take ownership of workflow definitions, runs, or GitHub state. Opening a linked resource rechecks the reader's current access.

Share to chat sends the task permalink to a selected conversation. Chat renders the link as a task card and includes it in Shared links. Sharing does not copy the task or grant access to it.

Workspace roles determine whether a member may read tasks, edit/comment/move work, or manage spaces, statuses, tags, sprints, and releases. If Tasks is absent, the active workspace or deployment does not currently provide that capability.