> For the complete documentation index, see [llms.txt](https://docs.opscanvas.io/oscar/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opscanvas.io/oscar/team-edition/team-assign/task-assignment.md).

# Task Assignment Flow

Oscar CLI allows team members to assign, track, and resolve tasks related to health check findings. This document walks through the complete task assignment workflow.

## Overview

The task assignment flow involves two roles:

* **Assigner**: Creates and assigns tasks to team members
* **Assignee**: Receives, reviews, and resolves or blocks assigned tasks

## Workflow

### 1. Assigner Creates Assignment

The assigner can assign health check findings to team members in two ways:

**Via command line:**

Use `/tasks assign` to assign a finding interactively.

![Task assignment](/files/Rp9VCGcRjOVDjvIZs2N6)

The command prompts for:

* Which finding to assign
* Team member to assign to
* Optional note with context

**Via web GUI:**

After running `/check health`, Oscar opens a local web interface where you can view findings and assign them by clicking on any finding to view details and select an assignee.

![Task assignment through GUI](/files/63ch4dUaYLrrI6qoBf28)

### 2. Assignee Sees Task Notification

When the assignee logs in to Oscar, they see pending tasks assigned to them at startup.

![Task notifications at startup](/files/OfcbgBsehCXpp1ldrSgt)

The notification shows:

* Number of open tasks
* Who assigned each task
* What needs attention
* Optional notes from the assigner

### 3. Assignee Resolves or Blocks Task

The assignee can take action on the task:

**Resolving a task:**

![Resolve task](/files/pDn92wZiAoMRWFRZxvPN)

Use `/tasks resolve` to mark the task as complete, with an optional resolution note.

**Blocking a task:**

![Block task](/files/uQWysSY4R8A5hYfdvXlr)

Use `/tasks block` to mark the task as blocked, with a required reason explaining the blocker.

### 4. Assigner Sees Resolution Notifications

When the assigner logs in, they see notifications about tasks that have been resolved or blocked.

![Resolved/blocked notifications](/files/6KuCEC5p5hzZCDJrMZkV)

The notification shows:

* Which tasks were resolved or blocked
* Who took the action
* Resolution notes or block reasons
* When the action was taken

## Available Commands

* `/tasks assign` - Assign a health check finding to a team member
* `/tasks reassign` - Reassign an existing task to a different team member
* `/tasks resolve` - Mark a task as resolved
* `/tasks block` - Mark a task as blocked with a reason
* `/tasks list` - View all your tasks (assigned to you or by you)

## Notes

* Tasks are tied to health check findings via `itemId` (e.g., `vpc_flow_logs/aws-prod-123`)
* Only one open task can exist per finding - reassigning updates the existing task
* Notifications appear at startup for both assignees and assigners
* All actions require team mode (`/team login`)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.opscanvas.io/oscar/team-edition/team-assign/task-assignment.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.