> For the complete documentation index, see [llms.txt](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/get-started/ticketing.md).

# Connect Ticketing

Connect Jira, Linear, Shortcut, or GitHub Issues so Heeler can open, update, and close tickets for findings.

Heeler runs a **two-way** integration with your issue tracker: it opens a ticket for a finding, comments as remediation progresses, and detects when the ticket is closed so the finding stays in sync. It also harvests projects, users, and teams to help automate ticket context.

## Supported trackers

<table data-view="cards"><thead><tr><th></th><th></th><th data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Jira Cloud</strong></td><td>OAuth — authorize Heeler in a click.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/get-started/ticketing/jira-cloud.md">Jira Cloud</a></td></tr><tr><td><strong>Jira (Legacy/On-prem)</strong></td><td>Self-hosted — server URL + API token.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/get-started/ticketing/jira-legacy-on-prem.md">Jira (Legacy/On-prem)</a></td></tr><tr><td><strong>Linear</strong></td><td>OAuth — authorize your workspace.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/get-started/ticketing/linear.md">Linear</a></td></tr><tr><td><strong>Shortcut</strong></td><td>API token + workspace URL.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/get-started/ticketing/shortcut.md">Shortcut</a></td></tr><tr><td><strong>GitHub Issues</strong></td><td>Reuses your GitHub connection — no new credential.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/get-started/ticketing/github-issues.md">GitHub Issues</a></td></tr></tbody></table>

{% hint style="info" %}
Once connected, give each team its own project/destination with [Team Ticket Settings](/mrecEO40m5D6bt7Pq5pE/get-started/map-your-organization/team-ticket-settings.md) — one workflow then routes every finding to the right team's tracker.
{% endhint %}


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/get-started/ticketing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.