> 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](https://545396582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYOS1iTqmWKUIHFRd1Kze%2Fuploads%2Fgit-blob-e17824e4c5b9ed7c16c2caaed11215f088cc683f%2Ftask_assignment.png?alt=media)

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](https://545396582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYOS1iTqmWKUIHFRd1Kze%2Fuploads%2Fgit-blob-01503d340cff3be4c8025c17c6660269392b8777%2Ftask_assign_GUI.png?alt=media)

### 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](https://545396582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYOS1iTqmWKUIHFRd1Kze%2Fuploads%2Fgit-blob-f20c16173ab1e4518e4ade3427cfa095f711fc01%2Ftask_notifications_at_startup.png?alt=media)

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](https://545396582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYOS1iTqmWKUIHFRd1Kze%2Fuploads%2Fgit-blob-31d410d12e90ddfd6066cef489a4e2c8090931da%2Fresolve.png?alt=media)

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

**Blocking a task:**

![Block task](https://545396582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYOS1iTqmWKUIHFRd1Kze%2Fuploads%2Fgit-blob-a4f7438eff4088947ba1aaf6b2d8029e7557a889%2Fblock.png?alt=media)

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](https://545396582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYOS1iTqmWKUIHFRd1Kze%2Fuploads%2Fgit-blob-4646286abda9980f4262d1585784e96afdd2532c%2Fresolved_or_blocked_notifications.png?alt=media)

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`)