> ## Documentation Index
> Fetch the complete documentation index at: https://docs.siftstack.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Triage and close out flagged issues

> Work through a Report's Annotations: assign, update, and resolve issues to drive a review to completion

After completing this topic, you can work through a Report's Annotations systematically: assigning, updating, and closing out every flagged issue.

<Note>
  New to Detect and Review? Read the [Overview](/documentation/review/overview) to understand how Rules, Reports, Annotations, and Campaigns work together before proceeding.
</Note>

## When to use this workflow

Use this workflow when a Report has been generated and you need to work through its Annotations systematically:

1. Filtering by status or owner
2. Distributing work across teammates
3. Adding evidence
4. Driving every issue to a final state

This is the day-to-day workflow for reviewers. It picks up where [Detect and review issues in a Run](/documentation/review/detect-and-review-issues-in-a-run) leaves off and covers the full range of tools available for managing Annotations at scale.

## Before you begin

* At least one Report exists for the Run you are reviewing. If not, see [Detect and review issues in a Run](/documentation/review/detect-and-review-issues-in-a-run).
* You have the team members' names available if you plan to assign Annotations.

## Complete the workflow

### Filter Annotations by state or assignee

The **Annotations** tab provides a workspace-level view of all Annotations across all Runs. Use the filters at the top to narrow down to the issues you want to work on:

* Filter by **Status** (Open, Failed, Accepted) to see only unreviewed or in-progress items.
* Filter by **Assignee** to see only the issues assigned to a specific team member.
* Filter by **Asset**, **Run**, or **Rule** to focus on a specific scope.

You can also access Annotations directly within a Report by clicking a Rule and then an Annotation in the Rules section.

### Assign issues to teammates

1. In **Sift**, click the **Annotations** tab.
2. In the **Annotations** table, click the Annotation you want to assign.
3. In the **Assigned to** selector, choose a team member.

Assignment changes are recorded in the activity log alongside comments and state transitions, so the full history of ownership is preserved.

### Add a comment

1. In the Annotation details panel, locate the comment thread.
2. Type your notes in the comment box. Comments support rich text.
3. Click **Post**.

Use comments to document your reasoning when making a review decision, flag follow-up actions, or provide context for the next reviewer.

### Attach a file to an Annotation

To attach a file directly to an Annotation:

1. In **Sift**, click the **Annotations** tab.
2. In the **Annotations** table, click the Annotation you want to attach a file to.
3. In the **File attachments** section, click **Attach**.
4. Upload the file.

To attach a file to a specific comment on an Annotation:

1. In the comment, click **Attach**.
2. Upload the file.
3. Click **Post**.

For supported file types and size limits, see [Annotations reference](/documentation/reference/annotations-reference).

### Download an attached file

To download a file attached to an Annotation:

1. In the **File attachments** section, expand it.
2. Hover over the file you want to download.
3. Click **Download**.

To download a file attached to a comment, locate the comment, hover over the file, and click **Download**.

### Move an Annotation through its states

In the Annotation details panel, use the status control to transition the Annotation:

* **Open** → **Failed**: the telemetry represents a real problem that must be addressed.
* **Open** → **Accepted**: the finding was reviewed and determined to be valid or not requiring action.
* **Failed** or **Accepted** → **Open**: reopen the Annotation if new information changes the assessment.

For the full list of valid state transitions, see [Annotations reference](/documentation/reference/annotations-reference).

<Info>
  Phase Annotations do not support state changes or assignment. Only Data Review Annotations have the status workflow described above.
</Info>

### Archive a resolved Annotation

Once an Annotation is fully resolved and no longer needs to appear in the active view, archive it:

1. In the Annotation details panel, scroll to the bottom and click **Archive**.
2. Confirm in the dialog.

Archived Annotations are soft-deleted. They no longer appear in the tree or on charts but can be restored. To restore an archived Annotation, locate it in the archived view and click **Restore**.

## Verify the result

A triage pass is complete when:

* Every Data Review Annotation in the scope of your review has a state of **Failed** or **Accepted**, and none remain **Open**.
* Issues requiring follow-up have an assignee and a comment explaining the next action.
* Supporting evidence (screenshots, logs, or other files) is attached to Annotations where context is needed.

## Next steps

* To track progress across a multi-Run effort, see [Track a multi-run review campaign](/documentation/review/track-a-multi-run-review-campaign).
* To share a Report with a stakeholder, open the Report, hover over its title, and click **Share** to copy a link to your clipboard.

## Reference

* [Annotations reference](/documentation/reference/annotations-reference)
* [Annotations reference](/documentation/reference/annotations-reference)