> For the complete documentation index, see [llms.txt](https://documentation.taskmaverick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.taskmaverick.com/missions/how-to-guides/trigger-one-ticket-for-multiple-issues.md).

# Trigger one Ticket for multiple issues

When a Mission has multiple questions that could each trigger a [Ticket](/missions/what-are-missions/ticket.md), you might end up with 5 separate Tickets for what is essentially one problem. Single Ticket solves this — no matter how many answers meet the trigger condition, only **one Ticket** is created.

## Why use Single Ticket?

A 30-question equipment maintenance [Checklist](/missions/what-are-missions/checklist.md) has Tickets attached to 12 questions. If an employee reports problems on 8 of them, without Single Ticket you'd get 8 separate Tickets flooding the [Ticket Board](/mobile-app/your-mobile-boards.md#ticket-board). With Single Ticket enabled, all 8 failed answers produce **one** consolidated "Maintenance Request" Ticket — and all triggering responses are recorded inside it.

**Without Single Ticket:** 8 problems → 8 Tickets → clutter, duplicate work, confusion about which Ticket covers what.

**With Single Ticket:** 8 problems → 1 Ticket → one clear record with all issues listed inside.

## How to set it up

1. Open a Mission Builder
2. Click **"+ Single Ticket"** at the top right of the Builder
3. Select the Ticket that should be used for this Mission

Once enabled, every question that allows a Ticket attachment will show only the pre-selected Ticket — you can't assign different Tickets to different questions within this Mission.

## How it works on mobile

When an employee [completes](/mobile-app/perform-a-mission.md) the Mission and multiple responses trigger the Single Ticket, the triggered responses are **highlighted** on the Mission details screen — showing exactly which answers caused the Ticket.

The Ticket itself appears on the destination [Ticket Board](/mobile-app/your-mobile-boards.md#ticket-board) as a single item. Managers opening it can see all the triggering conditions in one place.

## Good to know

* Only **one Ticket type** can be linked to a Mission when Single Ticket is active
* Single Ticket applies to the **Builder only** — Tickets configured in [Mission Settings](/missions/how-to-guides/configure-mission-settings.md) (like Ticket on Timer or Ticket on Rating) are separate and not affected
* Available for [Surveys](/missions/what-are-missions/survey.md), [Checklists](/missions/what-are-missions/checklist.md), [Tests](/missions/what-are-missions/test.md), and [Audits](/missions/what-are-missions/audit.md) — any Mission type that has questions with Ticket attachments


---

# 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://documentation.taskmaverick.com/missions/how-to-guides/trigger-one-ticket-for-multiple-issues.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.