> For the complete documentation index, see [llms.txt](https://learn.heeler.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.heeler.com/tenant-admin-guide/program/ticket-status.md).

# Ticket Status

## Viewing the Status of Tickets Created via Heeler

The **Ticket Status** page lists every ticket Heeler has created in your connected ticketing tools — whether opened manually from inside the product or automatically by a workflow. Use it to confirm tickets are flowing, see what state they're in, and click through to the originals.

### Where to find it

Administration → **Program** → **Ticket Status** in the left sidebar.

URL: `https://app.heeler.com/administration/program/ticket_status`

### Quick start

The page loads with all Heeler-created tickets in reverse-chronological order. To narrow down:

1. Use the filter chips at the top — **Type**, **Status**, **Workflow**, **Repository** — to scope to what you care about (e.g., "all SCA tickets currently *To Do*").
2. Use **All Filters** for finer control if the chips don't cover it.
3. Use the search box (top-right) for free-text matching against titles.
4. Click any **Ticket** ID to open the ticket in its source system.

> *Tickets listed here are ones that have been created by the platform, either manually via the product or automatically through Workflows.*

## Reference

### Columns

| Column         | Description                                                                                                                                                                   |
| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Title**      | The ticket's title — usually generated by Heeler to summarize the underlying finding (e.g., *"Rotate leaked credential in …"*, *"License violation: org.dom4j:dom4j 2.1.4"*). |
| **Type**       | Finding type the ticket was opened for. Common values include **SCA**, **SAST**, **SECRET**, and **LICENSE VIOLATION**.                                                       |
| **Repository** | The repo the ticket is associated with, shown as repo name + owner.                                                                                                           |
| **Ticket**     | The external ticket ID (e.g., a Jira `ENG-8746` or Linear `HD-1007`). Clicking opens the ticket in the source system.                                                         |
| **Status**     | The current status of the ticket in its source system (e.g., **TO DO**, **IN PROGRESS**, **DONE**).                                                                           |
| **Created**    | When the ticket was created. Sortable.                                                                                                                                        |

### Filters

* **Type** — limit to a single finding type (SCA, SAST, Secret, License Violation, etc.).
* **Status** — limit by ticket status as reported by the source system.
* **Workflow** — limit to tickets created by a specific Workflow. Useful when validating a new workflow.
* **Repository** — limit to a specific repository.
* **All Filters** — opens a panel for combining additional filters.

The **Search** box performs free-text matching against the title.

### What this page is not

This page is a **view**, not a configuration surface. There are no controls here to map ticket statuses, choose ticket projects, or change ticketing defaults. Those configuration tasks live elsewhere:

* **Where tickets land** (project, issue type, per-team defaults): Connection Mapping → Ticketing
* **Which integrations are available**: Integrations
* **What triggers a ticket**: Workflows

### How tickets get here

A row appears on this page whenever Heeler creates a ticket. Two paths produce that:

1. **Manually** — a user opens a ticket from a finding inside Heeler.
2. **Automatically** — a Workflow fires on an event (e.g., *New SCA finding detected*) and includes a *Create Ticket* action.

Heeler does not list tickets created independently in your ticketing tool — only the ones it opened itself.


---

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

```
GET https://learn.heeler.com/tenant-admin-guide/program/ticket-status.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.