> ## 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.

# Ticketing

> Turn findings into tracked work items in Jira, Linear, or GitHub Issues

Ticketing integrations create tracked work items — tickets or issues — from OASM findings, so remediation moves through the same system your team already uses.

## Availability

Ticketing is not available yet. OASM does not currently ship a connectable ticketing integration.

| Application | Status |
| - | - |
| Jira | Planned. A configuration schema exists but the application is disabled. |
| Linear | Planned. Not part of the active catalog. |
| GitHub Issues | Planned. Not part of the active catalog. |

Ticketing applications do not appear as connectable cards in the **Applications** tab until they are enabled. When they become available, each will have its own setup guide here.

## What to expect

When ticketing ships, the flow will follow the same pattern as the other integrations:

1. Connect the ticketing application with its API credentials.
2. Choose which findings should create tickets.
3. OASM opens a ticket when a matching finding is reported.

Until then, use a [Webhook](/integrations/webhook) integration to forward findings into your ticketing system through an adapter you control.

## Related

<Card icon="webhook" title="Webhook" horizontal href="/integrations/webhook">
  Forward findings to a ticketing system today
</Card>

<Card icon="plug" title="Integrations overview" horizontal href="/integrations/overview">
  Learn how connections and categories work
</Card>

<Card icon="triangle-alert" title="Vulnerabilities" horizontal href="/vulnerability">
  Review the findings you will ticket
</Card>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.