> 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/setting-a-ticket-live.md).

# Setting a Ticket Live

## Testing Ticket Configuration <a href="#e-ticket-follow-up" id="e-ticket-follow-up"></a>

Once you are happy with your Ticket configuration, you can test it in Work Manager.

{% embed url="<https://enate.cdn.spotlightr.com/watch/MTM2MjYxOA==>" %}

## Setting a Ticket Live

To set a Ticket live, click 'Save'. If there are any validation issues, they will need to be sorted. Once you have saved any further changes, you can now set the Ticket live.&#x20;

![](/files/-MWp1nzlu6pf3_spQOfh)

You can also set a Ticket live from the Service Matrix Screen, provided it is in a state of Validated Changes, or Live with Validated Changes:

![](/files/455QY2yL2zvEmL0DNdTY)

You can also set a Ticket live from the Service Matrix if it is in a state of 'Draft' or 'Live with Draft changes'. When you click to set live a Ticket that is in either of these two states, the system will run a validation check. If the validation of the Ticket encounters an error, a error message will be displayed stating that the Ticket could not be set live and directing you to open up the Ticket process to deal with the validation errors before attempting to set the Ticket live again.

## Ticket Feedback <a href="#e-ticket-follow-up" id="e-ticket-follow-up"></a>

Setting whether a Ticket will allow feedback is now done in the Ticket type settings in the Service Lines screen. [See here for more details](/enate-help/builder/builder-2021.1/service-lines-screen/creating-ticket-case-and-action-types-in-a-service-line.md#c-creating-a-new-type-of-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 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/setting-a-ticket-live.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.
