> For the complete documentation index, see [llms.txt](https://docs.adminremix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adminremix.com/help-desk/all-tickets.md).
# All Tickets
If you have permissions, you will have access to view and change status of all tickets here. You can also create tickets for yourself or others.
## 1 - Creating a Ticket for Yourself
1. Click the "+ button" in the top right on the screen.
2. Select "Request Help for Yourself"
3. Select which type of ticket you are requesting service for.
4. Choose your item and the issue reason for the ticket.
5. Submit your ticket. It will automatically populate in your ticket field after submission.
## 2 - Create a Ticket for Someone Else
See our "[Request Help](/help-desk/request-help/creating-a-ticket-for-others.md)" tab to see how to create a ticket for someone else.
## 3 - Different Views
Change the view of your All Ticket dashboard from our normal table view.
You can change how many columns you view by clicking the table with the number next to it, and selecting the headers you'd like to see.
To view you tickets in a column view by status order, select the far right "Column View" button.
In this view, you can move tickets from one column to another by dragging and dropping them.
You can also edit, delete, issue a fine, or assign a ticket to an agent by clicking the 3 dots on the right side of the ticket. 
---
# 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://docs.adminremix.com/help-desk/all-tickets.md?ask=&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.
