> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/enate-help/builder/builder-2021.1/ticket-configuration/creating-a-new-ticket-process.md).

# Cloning from existing Ticket settings

Upon opening the Ticket configuration screen, if you have not yet started to add any Ticket category definitions you will be met with the ‘Clone’ popup. This lets you copy categories and configurations from existing Tickets. Processes from a different Ticket type will be highlighted in grey with a yellow border.

![](/files/-MWp12nbdSU87kFj3zUn)

You can filter the processes by customer, contract and service. Contract options will be based the customer selection and the service options will be based on the customer and contract selections. 

The Same Process Types Only toggle lets you choose to only view Ticket processes that have the same process type. It is disabled by default.

![](/files/-M_QrEHbpoT-yIHOFmkN)

Once you have selected a source,  the categories and configurations from that existing Ticket will be cloned into your new Ticket's screen.


---

# 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://docs.enate.net/enate-help/builder/builder-2021.1/ticket-configuration/creating-a-new-ticket-process.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.