Tasks

Tasks is the shared workspace queue for follow-up work. Tasks can be created manually, from an incident, or by an automated workflow.

Task fields

A task can include:

• title and description;
• program;
• status;
• priority;
• owner or assignees;
• reviewer;
• due date;
• linked artifact or originating context; and
• comments.

Available statuses are Not Started, In Progress, Blocked, Done, and Archived. Priorities are Low, Medium, High, and Urgent.

Create a task

1. Open Tasks and select the create action.
2. Enter a short, action-oriented title.
3. Add enough description for the assignee to understand the desired outcome.
4. Set priority, status, owner, and due date where appropriate.
5. Add the program or related context if the task belongs to a larger initiative.
6. Save the task.

Tasks created from an incident or workflow can already contain source context. Review generated titles, descriptions, owners, and dates before relying on them.

Manage the queue

Use the open and completed groupings, search, filters, and sorting to focus the list. Open a task to update its fields, mark it done, archive it, or delete it when removal is appropriate.

Use Blocked when work cannot continue and document the dependency in the description or a comment. Use Archived for work that should remain recorded but is no longer part of the active queue.

Comments and collaboration

Comments preserve progress, decisions, and handoffs without replacing the task description. Add a comment when the update is chronological; edit the task description when the core requirement itself changes.

Comments can be edited or deleted through the available actions. Avoid placing credentials or unnecessary customer-sensitive data in a task or comment.

Related product behavior

• Home previews open tasks and their due dates.
• Incidents can create follow-up tasks.
• Workflows can create tasks and bind values from earlier steps into task fields.
• Artifacts can be linked when generated output is part of the work.

Completing a task does not automatically resolve a related incident unless a user or configured automation performs that separate action.

Recommended operating practice

• Use one accountable owner when responsibility is clear.
• Reserve Urgent for genuinely time-critical work.
• Add a due date when lateness changes the business outcome.
• Explain why a task is blocked and what will unblock it.
• Link or name the incident, report, call, artifact, or workflow when context is not obvious.
• Close or archive stale tasks so open-work views remain trustworthy.