> 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/connection-mapping/ticketing.md).

# Ticketing

The **Ticketing** sub-section of Connection Mapping is where you configure the general default settings for ticket creation in your ticketing system(s). 

Each [Team can also have its own ticketing project, issue type, and field defaults](/tenant-admin-guide/connection-mapping/teams.md#per-team-settings) — so when a workflow opens a ticket for a finding on Team A's repo, it lands in Team A's queue with the right metadata.

### Where to find it

Administration → **Connection Mapping** → **Ticketing** in the left sidebar.

URL: `https://app.heeler.com/administration/connection_mapping/ticketing`

### Prerequisites

Before configuring Ticketing, you need:

1. A ticketing tool connected via Integrations (Jira, Linear, or Shortcut).

### Reference

* **Project** (required) — Project from the selected connection where tickets will be created.
* **Ticket Type** (required) — Default type applied to new tickets.
* **Team** (optional) — Default team assigned to new 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:

```
GET https://learn.heeler.com/tenant-admin-guide/connection-mapping/ticketing.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.