> For the complete documentation index, see [llms.txt](https://help.glpi-project.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.glpi-project.org/faq/plugins/more-options.md). # More options ### How do I set up More Options? A [procedure](/doc-plugins/plugins-glpi/more_options.md) is available to guide you through setting up the plugin. *** ### What is More Options used for? MoreOptions adds options to tickets, changes and problems: automatic assignment of groups and technicians, mandatory fields before solving or closing, mandatory fields on tasks and, from version 1.1, the escalation of an item between groups. *** ### Which version of GLPI do I need? * MoreOptions **1.0** requires GLPI **11.0** minimum. * MoreOptions **1.1** requires GLPI **12.0** minimum and adds the escalation features. *** ### Where is the plugin configured? In **`Administration`** > **`Entities`** > (an entity) > **`More options`**. The **`Configure`** button of the plugin in **`Setup`** > **`Plugins`** opens the same tab for the active entity. All the settings are set **per entity**. On a child entity, every option can be set to **Inherit** to use the value of the parent entity. *** ### Does MoreOptions replace the Escalade plugin? Yes, from GLPI 12. Escalade reaches its end of life and its escalation features are provided by MoreOptions 1.1. Update Escalade to its End Of Life version, then migrate its group filter to MoreOptions, from the interface or with the command `php bin/console plugins:moreoptions:migrate_escalade`. More information [here](https://app.gitbook.com/s/uUCcURk2xlvtpVGbiRZf/plugins-glpi/moreoptions#migrating-from-the-escalade-plugin). *** ### Can the groups of the requester or of the technician be assigned automatically? Yes. In the **Ticket**, **Change** and **Problem** tabs, the options **Take the requester group** and **Take the technician group** add the groups of the user (default group only, or all groups) when they are added as requester or as assigned technician. *** ### Can the technical manager or group of a category be assigned automatically? Yes, with the options **Assign technical manager when changing category** and **Assign technical group when changing category**. *** ### Can I force some fields to be filled before solving or closing a ticket? Yes. In **Mandatory fields to solve and close ITILs**, you can require a technician, a technicians group, a category, a location and a solution. While a field is missing, **Add a solution** is locked and its tooltip lists the missing fields. *** ### Can I prevent closing a ticket while tasks are not done? Yes, with the option **Prevent closure with tasks in To Do status**. *** ### Can I make some task fields mandatory? Yes. In the **Tasks** tab, you can require the category, the duration, the user and the group of the tasks. These settings are shared by tickets, changes and problems. *** ### Why don't I see the Escalate button? Check that: * MoreOptions is in version **1.1** or later (GLPI 12); * **Activate escalation** is enabled in the **Escalate** tab of the entity of the item; * you are allowed to assign the item: the button is only shown to these users. *** ### Why can I only escalate to some groups? The **group filter** is probably enabled in the **Escalate filter** tab. An item can then only be escalated to the next level of the escalation tree of the entity. Profiles selected in **Profiles allowed to bypass the filter** can escalate to any group. *** ### Can a business rule escalate a ticket? Yes. The rules for tickets, changes and problems have an **Assign — Escalate to group** action, which works like a manual escalation. The **Check rules** button of the **Escalate** tab lets you switch existing **Technician group** actions to **Escalate to group**. *** ### What happens to my rules if I uninstall the plugin? The **Escalate to group** actions are switched back to the core **Technician group** action, so that the rules keep assigning a group. --- # 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://help.glpi-project.org/faq/plugins/more-options.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.