Set task properties and ownership
Keep priority, assignment, source context, and delivery state clear.
Task properties help the team decide who owns an outcome and what should happen next. Open a task's detail page to edit the controls your role permits.
Set useful properties
| Property | Use it for |
|---|---|
| Title and description | The outcome, constraints, and acceptance |
| Priority | Relative urgency within the team's queue |
| Labels | Shared categories for search and filtering |
| Repositories | Source context needed for delivery |
| Agent assignment | The role responsible for agent work |
| Human assignment | The teammate responsible for follow-through |
| Status | The task's current workflow state |
An assigned agent and a human owner are different forms of responsibility. Assigning an agent does not establish that execution has started. Follow the task's linked session to verify active work.
Edit without losing context
Keep the description brief and link to detailed specifications or evidence. When changing scope, explain the decision in activity or the task conversation. Review dependencies before moving work forward; a status change may be rejected when its requirements are not satisfied.
Manual status changes pause automatic progression. If you want Uno to evaluate the task from its current evidence again, use the task's automatic-update controls. See task progress.
Cancel or mark a duplicate
Cancel work that should no longer be delivered. Cancelling a task does not automatically stop every linked session; inspect any active execution separately.
For duplicate work, choose the original task in the same workspace using the duplicate action. The original remains the delivery reference. Duplicate tasks do not satisfy a prerequisite as completed work. Use the offered undo action if the duplicate relationship was wrong; review the restored status and automation state.
For work breakdown and ordering, see dependencies.