> For the complete documentation index, see [llms.txt](https://documentation.movatic.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.movatic.co/admin-site/maintenance/tickets-tab.md).
# Tickets Tab
Once you clock the maintenance link. You will see two tabs at the top of the screen which is Tickets and Logs.
Here are the information you can see under the ticket tab.
You will have an option to filter your view on what ticket you want to check. You can filter it to open, closed or cancelled maintenance tickets.
Now let's talk about the column options on top of the maintance ticket.
1. Actions - there will be a pencil icon under action that will allow you to edit or modify your maintenance ticket.
2. Due - it is the date when the ticket will be due. You can also click the 3 lights beside it to filter the date in ascending or descending order.
3. Priorty - it will let you know if the ticket has priority or not. There are 5 level of priority as follows:
* 1 - Lowest
* 2 - Low
* 3 - Normal
* 4- High
* 5 - Highest
4. Assignee - will show you in which person or technician the ticket was assigned.
5. Unit - it will show you the hardware number (bike, locker, kayak number)
6. Description - will give a brief summary of the issue the customer encountered.
---
# 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://documentation.movatic.co/admin-site/maintenance/tickets-tab.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.
