> 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/map-your-organization/ticket-closing.md).

# Ticket Closing

Control whether and when Heeler closes or comments on its Jira and Linear tickets as vulnerabilities are remediated — and the status it moves them to.

When Heeler opens a ticket for a finding, it can also **close that ticket automatically** once the finding is remediated — and comment along the way. **Ticket Closing** is where you set that behavior, per Jira or Linear connection.

{% hint style="info" %}
This is the **Ticketing** tab under **Administration → Connection Mapping**. It configures *closing* behavior for tickets Heeler already creates — it doesn't create the connection. Connect the tracker first under [Configure Integrations → Ticketing](/mrecEO40m5D6bt7Pq5pE/get-started/ticketing.md).
{% endhint %}

## Before you start

* **Administrator** in Heeler.
* A connected **Jira** or **Linear** integration. (GitHub Issues closure is detected automatically and isn't configured here.)

## Where it lives

Open **Administration → Connection Mapping → Ticketing**. Each connected Jira and Linear integration gets a **Ticket Closing** card; pick the connection to configure it.

## Close policy

For each connection, choose how Heeler closes its tickets as remediation progresses:

<table><thead><tr><th width="330">Setting</th><th>What it does</th></tr></thead><tbody><tr><td><strong>Close when the fix is merged (code fix)</strong></td><td>Close the ticket as soon as the fixing change lands in code. This is terminal — when it's on, the deployment options below don't apply.</td></tr><tr><td><strong>Close when all deployments are resolved</strong></td><td>Wait until the finding is resolved across every running deployment (not just merged) before closing — the stricter, "fixed in production" bar.</td></tr><tr><td><strong>Comment when deployments are resolved</strong></td><td>Post a progress comment instead of closing, so the owning team decides when to close.</td></tr></tbody></table>

## The status Heeler moves tickets to

Heeler needs to know which tracker status means "closed" so it transitions tickets correctly:

{% tabs %}
{% tab title="Jira" %}
Choose the target **Status** Heeler moves a ticket to when it closes it. You can set a connection-wide default (a global **Done**-category status) and, if your projects differ, scope the status per **Project** and **Issue Type**. Heeler follows your Jira workflow's transitions to reach that status.
{% endtab %}

{% tab title="Linear" %}
Choose the Linear workflow **State** Heeler moves an issue to when it closes it (typically a **Done**/completed-category state).
{% endtab %}
{% endtabs %}

## Related

* [Configure Integrations → Ticketing](/mrecEO40m5D6bt7Pq5pE/get-started/ticketing.md) — connect Jira, Linear, or GitHub Issues first.
* [Team Ticket Settings](/mrecEO40m5D6bt7Pq5pE/get-started/map-your-organization/team-ticket-settings.md) — route each team's tickets to the right project and channel.
* [Automate Remediation](/mrecEO40m5D6bt7Pq5pE/fix/automate-remediation.md) — the workflows that open and update these tickets.


---

# 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/map-your-organization/ticket-closing.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.