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

# Issue

> Track and manage security findings, tasks, and vulnerabilities with the issue management system

The Issue module is used to track, manage, and collaborate on security findings or tasks within the system.

An issue can represent a vulnerability, a detected event, or a manually created task. It serves as a central place for discussion, validation, and resolution.

***

## Overview

The Issues page displays a list of all issues with key information:

* **Status** — Current state (**Open** or **Closed**)
* **Title** — Issue name or description
* **Created by** — User or system
* **Created time** — When the issue was opened

You can filter issues by:

* **Status** (Open / Closed)
* **Search** by title or keyword

***

## Issue sources

Issues can be created in two ways:

### Manual creation

Users can create issues manually by clicking **Create Issue** and providing a title and description.\
This is useful for tracking tasks, investigations, or custom findings.

### Automatic creation

Issues can also be generated automatically when:

* A scan is triggered
* New vulnerabilities are detected

This ensures that newly discovered risks are tracked immediately without manual intervention.

***

## View issue details

To view an issue:

1. Click on an issue from the list
2. The issue detail page will open

The detail view includes:

* **Title and ID**
* **Status** (Open / Closed)
* **Author information**
* **Activity timeline**

***

## Comment and collaboration

Each issue supports discussion through comments.

You can:

* Add comments to provide context or updates
* Use comments to collaborate with team members
* Track conversation history over time

***

## Issue actions

### Close issue

* Click **Close issue** to mark it as resolved
* Closed issues are removed from active workflows but remain accessible

### Reopen issue

* Closed issues can be reopened if needed
* This allows continued tracking if the problem persists

***

## Labels

Issues can include labels (tags) to help categorize and organize them.

Examples:

* vulnerability type
* priority
* team ownership

***

## Workflow

A typical issue workflow:

1. Issue is created (manually or automatically from scan)
2. Team reviews the issue
3. Discussion and investigation via comments
4. Apply fixes or mitigation
5. Close the issue
6. Reopen if the issue reoccurs

***

<Info>
  Issues act as a collaboration layer on top of vulnerabilities, helping teams track resolution progress and communication.
</Info>