TASK MANAGEMENT
Give every task a clear place, owner and next step
Organize practical delivery work with project context, assignees, priorities, dates and a description that explains what completion means.
A task needs more than a checkbox
An action such as “prepare the proposal” becomes useful when the next person can see which project it belongs to, who is responsible and when the result is needed. Tsumira tasks carry that context together. Capture a small follow-up immediately or describe a larger deliverable in detail, then organize it within the project rather than maintaining a disconnected personal list.
Describe the work and its outcome
A task has a title and description, with support for structured description content where the editor is available. Add a start date, due date and estimated minutes when they help planning. A parent task and milestone can connect a small action to the wider deliverable. These fields describe the work itself; they do not imply that an estimate is a measured timesheet entry.
- Title and explanatory description
- Start date, due date and estimate
- Parent task and milestone association
Make ownership and status explicit
Assign active project colleagues and select a practical priority: low, normal, high or urgent. Task states distinguish backlog, ready, in progress, blocked, review, done and cancelled work. A blocked reason can explain why work cannot proceed. Keeping review separate from done helps a colleague ask for acceptance without presenting an unfinished result as complete.
- Multiple task assignees
- Seven meaningful task states
- Priority and blocked-work explanation
Keep customer context and changes coherent
A task normally inherits the project customer and can use its own supported CRM customer reference when the work requires a different relationship. Updates check the current record revision, helping prevent an older open screen from silently replacing newer changes. Creating a task without choosing a project uses an inbox container, so quick capture still has an organized home.
- Project customer inheritance with explicit override
- Concurrent-change checks when updating
- Inbox capture before choosing the final project
A concrete workflow
Capture the action
Write the required outcome and choose the project, or capture it in the inbox while the request is fresh.
Agree responsibility
Select the assignees, priority and dates so the people doing the work share the same expectation.
Work through the states
Move from ready to in progress; explain a blocker or request review when the next decision belongs to someone else.
Finish with context
Mark the accepted work done and leave any necessary handover in the relevant project conversation.
An illustrative working example
Example: preparing a customer workshop
A delivery lead creates “Prepare workshop agenda” under the customer project, assigns a facilitator and adds a due date before the session. A supporting task collects participant questions. When an external answer is missing, the facilitator marks the task blocked and records the reason. After the agenda is prepared, review signals that a colleague must check it before completion. The project retains the sequence without a second spreadsheet.
Questions about this topic
Can a task have more than one assignee?
Yes. Tasks support multiple assignees. Choose people who actually share responsibility and keep the description clear about who prepares the result and who reviews it.
What happens if I have not chosen a project?
Quick task creation can use the tenant inbox project. This supports capture without creating a task that has no underlying project context.
Are estimated minutes already billable time?
No. An estimate is a planning value. Actual time entries and their approval or billing treatment belong to the connected Time workflow.
Does moving a task to done issue an invoice?
No. Task completion describes delivery progress. Billing candidates, acceptance and financial documents follow their own controlled workflow.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Asana
Workflow concept: Map exported task titles, owners and dates before creating the project plan.
Jira (OAuth)
Workflow concept: Review issue descriptions and blocked reasons before a controlled task migration.
Linear
Workflow concept: Translate issue ownership into explicit project-task responsibilities.