> For the complete documentation index, see [llms.txt](https://ticketking.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ticketking.xyz/docs/get-help-and-community/reporting-bugs.md).

# Reporting bugs

How to file a useful bug report.

A clear bug report is the fastest way to get a fix.

## Where to report

* **Bugs.** Create a bug report ticket in `#create-a-ticket` in the support Discord at [ticketking.xyz/discord](https://ticketking.xyz/discord).
* **Security issues.** Email <support@ticketking.xyz> in private. Do not post security issues publicly.

## What to include

### 1. What you did

The steps to reproduce it. A numbered list works well:

> 1. Created a new ticket panel with the wizard.
> 2. Added 3 buttons.
> 3. Set Required Roles on the second button.
> 4. Clicked Save.

### 2. What you expected

> The panel should have saved with Required Roles set.

### 3. What actually happened

> The Save button said "Saved", but after a refresh Required Roles was empty.

### 4. Server ID

The Discord server ID where the bug happened.

### 5. Your browser or Discord client

For a dashboard bug, your browser, for example "Chrome 138 on macOS". For a bot bug, whether you used Discord on desktop, mobile, or web.

### 6. Screenshots or a recording

For anything visual, attach a screenshot. For a tricky sequence, a short screen recording helps a lot.

### 7. Time

Roughly when it happened.

### 8. How often

Did it happen once, every time, or sometimes?

## What not to include

* Other people's data. Do not paste members' DMs, payment information, and so on.
* You do not need to include your frustration. Just the facts help the fix.

## Found a bug in the docs?

Report it the same way. Typos, out-of-date information, and missing pages are all worth reporting.

## Related

{% content-ref url="/pages/dZKa2XV9PIaCVaCgC18j" %}
[Joining the support Discord](https://ticketking.xyz/docs/get-help-and-community/joining-support-discord.md)
{% endcontent-ref %}

{% content-ref url="/pages/9jDzQPjAcBq7TWsZVZON" %}
[Requesting features](https://ticketking.xyz/docs/get-help-and-community/requesting-features.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ticketking.xyz/docs/get-help-and-community/reporting-bugs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
