Work
Projects, tasks and requests
How a team plans and tracks work in Volobox: tasks and the requests behind them, boards and milestones, and agents that take tasks.
A project is where a team plans and tracks its work: tasks, the requests that lead to them, the views that show them, and the people and agents who do them. Product, operations and client teams use the same structure, and an agent takes a task in a project the way a person does.
Tasks and sub-tasks
A task has a state, assignees, a description and the fields a project turns on: priority, due date, milestone, area, type, labels and effort. Each task has its own discussion.
Its work state moves through To do, In progress, In review, Blocked and On hold. A task enters In review by itself while a pull request linked to it is open.
Tasks can be split into sub-tasks (one level deep), linked as Blocked by another task, and started from a project's task templates. Bulk edit changes status, milestone, area, type, priority, labels or assignees on many tasks at once.
Requests
A request is intake: a bug, an idea or a need, waiting for triage. Requests are handled by tasks.
- One task can handle several requests (Create one task).
- A request can be added to a task that already exists.
- A request closes by itself when the work on it is done.
Fill with AI drafts a request or task with your assistant, which writes only to the unsaved form.
Views, milestones, areas, labels and types
Tasks are shown through saved views, each a List or a Board, with a saved filter.
- Milestones group work into sprints, releases or phases with dates.
- Areas split a project by team or component, and can route new requests to a chosen person.
- Labels are lightweight tags.
- Types (Bug, Feature, Task and your own) say what kind of work an item is, for tasks and requests alike.
The project Overview summarizes open work, milestones and workload. On coding projects it adds a Delivery card with merge and cycle-time figures.
Assigning work to agents
A task can be assigned to one shared team agent that is a member of the project. The agent works under its own identity, with its own skills, tools and access, not the access of the person who assigned it.
On coding projects, a task's Coding mode (Auto, On or Off) decides whether the agent works in a coding session or replies in the task discussion. You can ask it to plan first and wait for approval, steer it from the discussion, and read its Agent confidence on the pull request it opens.
See Coding, and the guide From a task to a pull request.
Project guidance and learned notes
Agent guidance is a project's standing instructions for agents. It is added to their context in project chat, coding sessions and workflow runs about the project.
Learned notes are short statements of fact about how the project works ("we release on Thursdays"). An agent can propose one, and it is used only after a project Admin approves it. Guidance wins where the two disagree.
Note
Notes about pay, performance, health, HR or legal matters, credentials or personal details are refused.
Story
Story shows how work travelled: from a ticket or chat message to a request, the task made from it, workflow runs, coding sessions, pull requests and their reviews. It appears as an Activities feed and as a story map, and Stories lists what is moving across the workspace.
Volobox builds it from recorded activity and links. No AI writes or summarizes a story.
Sharing a project with a client
A project Admin who holds the permission to share projects can share chosen saved views with a Client. The client's external collaborators read those views in the Portal, open a read-only peek of a task, and open requests if the team allows it.
They never become project members and see nothing that was not shared. A public project is still not visible to them. See Support.
A project can also own Docs spaces and shared drives, so access follows project membership. See Docs and files.