> 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/doc-plugins/plugins-glpi/more_options.md).

# More Options

MoreOptions adds options to GLPI's ITIL objects (tickets, changes and problems): automatic assignment of groups and technicians, mandatory fields before solving or closing, mandatory fields on tasks, and a full **escalation** workflow between groups (manual escalation, a business rule action, and an escalation tree per entity).

All the settings are configured **per entity**, and child entities can inherit them from their parent.

## Sources

| Download                                              | Sources                                      |
| ----------------------------------------------------- | -------------------------------------------- |
| <https://github.com/pluginsGLPI/moreoptions/releases> | <https://github.com/pluginsGLPI/moreoptions> |

***

## Requirements (self-hosted)

| GLPI Version | Minimum PHP | Recommended |
| ------------ | ----------- | ----------- |
| 11.0.x       | 8.2         | 8.4         |
| 12.0.X       | 8.3         | 8.5         |

| MoreOptions version | GLPI version | Content                                                              |
| ------------------- | ------------ | -------------------------------------------------------------------- |
| **1.0**             | 11.0 minimum | Actors and groups, closure, mandatory fields, mandatory task fields. |
| **1.1**             | 12.0 minimum | Adds the escalation, which replaces the Escalade plugin.             |

{% hint style="info" %}
The escalation features (escalation, history, *Escalate to group* rule action, group filter and escalation tree, migration from Escalade) are only available from MoreOptions **1.1**, on **GLPI 12**.
{% endhint %}

{% hint style="info" %}
This plugin is available without a [GLPI Network](https://services.glpi-network.com/#offers) subscription. It is also available on [GLPI Cloud](https://glpi-network.cloud).
{% endhint %}

***

## Install the plugin

* Go to the marketplace. Download and install the plugin **MoreOptions**.
* Or from the command line: `php bin/console plugin:install moreoptions -u <admin>` then `php bin/console plugin:activate moreoptions`.

A configuration is created automatically for every entity. New entities get theirs when they are created, with every option set to *Inherit*.

{% hint style="warning" %}
**GLPI 12: MoreOptions replaces Escalade.** From GLPI 12, the Escalade plugin reaches its end of life and is replaced by MoreOptions 1.1. On an instance using Escalade, update Escalade to its End Of Life version, then migrate its group filter to MoreOptions: see [Migrating from the Escalade plugin](#migrating-from-the-escalade-plugin).
{% endhint %}

***

## Where to configure the plugin

The configuration is a tab of the entities: **Administration > Entities > (an entity) > More options**. The *Configure* button of the plugin in **Setup > Plugins** opens the same tab for the active entity.

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-69f82493381d12c4dd83d4af8641936cf949cbff%2Fmoreoptions_config_location.png?alt=media" alt="The &#x22;More options&#x22; tab of an entity"><figcaption></figcaption></figure></div>

The tab is split into six sub-tabs (four in version 1.0, without the escalation tabs):

| Sub-tab                             | Content                                                                                                                                |
| ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| **Ticket**, **Change**, **Problem** | Actors and groups, closure, mandatory fields to solve and close. The same settings exist for each ITIL type and are set independently. |
| **Tasks**                           | Mandatory fields when creating a task (shared by tickets, changes and problems).                                                       |
| **Escalate**                        | Activation and behaviour of the escalation.                                                                                            |
| **Escalate filter**                 | Group filter and escalation tree of the entity.                                                                                        |

**Rights:** the configuration requires the **Setup** right (`config`) of the profile; it is read-only with *Read* and editable with *Update*.

### Inheritance between entities

On the root entity, each option is simply *No* / *Yes* (or a list of values). On a child entity, every option also has an **Inherit** choice (the default). The badge on its left shows the value currently inherited from the parent entity.

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-475134d6612af0ce76e101a044812ba701a00745%2Fmoreoptions_config_child_ticket.png?alt=media" alt="Configuration of a child entity: every option inherits from the parent entity"><figcaption></figcaption></figure></div>

***

## Ticket, Change and Problem tabs

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-de70e46b2aee1f95a9eee6044b888e50808f76e9%2Fmoreoptions_config_ticket.png?alt=media" alt="Ticket tab of the configuration"><figcaption></figcaption></figure></div>

### Actors and groups

| Option                                              | Values             | Behaviour                                                                                                                                                    |
| --------------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Take the group of associated item**               | No / Yes           | When an item (computer, printer…) is linked to the ticket/change/problem, its groups are added as **assigned groups**.                                       |
| **Take the requester group**                        | No / Default / All | When a user is added as **requester**, their groups are added as requester groups: *Default* = the user's default group only, *All* = all the user's groups. |
| **Take the technician group**                       | No / Default / All | Same thing for a user added as **assigned technician**: their groups are added as assigned groups.                                                           |
| **Assign technical manager when changing category** | No / Yes           | When the item is updated and has a category, the **technical manager** of the category is added as an assigned technician.                                   |
| **Assign technical group when changing category**   | No / Yes           | Same thing with the **group in charge** of the category, added as an assigned group.                                                                         |
| **Assign technician from task to parent item**      | No / Yes           | When a task is created with a technician, this technician is added as an assigned technician of the ticket/change/problem.                                   |

A group is only added if its settings allow it for that role (*Requester*, *Assigned to*…), and never twice.

{% hint style="warning" %}
**Compatibility with the Escalade plugin (tickets only).** Escalade has its own global option *Use the technician's group*. When it is effectively enabled, it takes precedence over **Take the technician group** for tickets: MoreOptions then skips its own processing and shows a warning next to the option, as in the screenshot above. The Behaviors plugin is also taken into account, as Escalade steps aside for it on ticket creation.
{% endhint %}

### Closure

| Option                                         | Behaviour                                                                                                                                                                                         |
| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Prevent closure with tasks in To Do status** | The ticket/change/problem cannot be solved or closed while one of its tasks is in *To do* status. The user gets the message *"The ticket you wish to close has tasks that need to be completed."* |

### Mandatory fields to solve and close ITILs

The fields set to *Yes* must be filled before the item can be solved or closed (by adding a solution, or by changing its status):

* **Technician**: at least one assigned technician. On tickets, when GLPI is set to assign the solution author as technician, this is accepted.
* **Technicians group**: at least one assigned group.
* **Category**
* **Location**
* **Solution**: when the status is changed directly to *Solved* or *Closed*, a non-refused solution must exist.

The check is done on the server side: when fields are missing, the action is refused with the message *"To close this Ticket, you must fill in the following fields:"* followed by the list.

The user is also warned beforehand: in the **Answer** menu of the timeline, **Add a solution** is greyed out with a lock, and its tooltip lists the missing fields.

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-e23318f05662a0237766e3f2f9d7f608cbef2cb0%2Fmoreoptions_solution_warning.png?alt=media" alt="Add a solution is locked while required fields are missing"><figcaption></figcaption></figure></div>

***

## Tasks tab

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-06cd8afee11763b21ffbc44fcd219794d824e222%2Fmoreoptions_config_task.png?alt=media" alt="Tasks tab of the configuration"><figcaption></figcaption></figure></div>

The fields set to *Yes* are mandatory when **creating a task** of a ticket, change or problem: **Category**, **Duration**, **User** (technician in charge) and **Group** (group in charge). These settings are shared by the three ITIL types.

In the task form, the mandatory fields are marked with a red asterisk, and the form cannot be submitted until they are filled:

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-1f3fadfbd6af040a9ca12a53dafadebe9a2e5dfa%2Fmoreoptions_task_mandatory.png?alt=media" alt="Task form with mandatory Category and Duration"><figcaption></figcaption></figure></div>

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-376d5ea59b9df7001373f9a61952990f9d4f3c30%2Fmoreoptions_task_mandatory_error.png?alt=media" alt="Message shown when mandatory task fields are missing"><figcaption></figcaption></figure></div>

The same check is done on the server side, so tasks created another way (API, mail collector…) are refused too.

***

## Escalation

The escalation lets a technician hand a ticket, change or problem over to another group, keeping a trace of it in the timeline.

{% hint style="info" %}
Available from MoreOptions **1.1** (GLPI 12). The *Escalate* and *Escalate filter* tabs do not exist in version 1.0.
{% endhint %}

### Escalate tab

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-2460c3aea6f9677b1151aa623b8e85310b84dd5f%2Fmoreoptions_config_escalate.png?alt=media" alt="Escalate tab of the configuration"><figcaption></figcaption></figure></div>

| Option                                                | Behaviour                                                                                                             |
| ----------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| **Activate escalation**                               | Enables the escalation for the items of the entity: *Escalate* button, timeline entries and the business rule action. |
| **Remove technician after escalation**                | The assigned technicians are removed from the item once it is escalated.                                              |
| **Ticket / Change / Problem status after escalation** | Status set on the item after the escalation, or *No change*.                                                          |
| **Assign me as observer after escalation**            | Default value of the matching switch in the escalation form.                                                          |
| **Escalate event is private**                         | Default value of the *Private* switch in the escalation form (also used for escalations made by business rules).      |

When business rules assign a technician group, a banner at the bottom of this tab links to the **Check rules** page (see [Escalate to group rule action](#escalate-to-group-rule-action)).

### Escalating an item

When the escalation is enabled, an **Escalate** button is shown next to the **Assigned to** field of the item. It is only shown to users who are allowed to assign the item.

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-8bb29150ee53795c40ef1386241f63dccc13d3f5%2Fmoreoptions_escalate_button.png?alt=media" alt="Escalate button next to Assigned to"><figcaption></figcaption></figure></div>

It opens the escalation form:

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-45e2bc4b544591ec5b0f6daa42809d8a8115ef00%2Fmoreoptions_escalation_form.png?alt=media" alt="Escalation form"><figcaption></figcaption></figure></div>

* **Comment** (optional, rich text): the reason for the escalation.
* **Group** (required): the target group. Only groups that can be assigned and are visible from the entity of the item are offered; groups already assigned are excluded.
* **Assign me as an observer** (eye icon): adds the author of the escalation as an observer of the item.
* **Private** (lock icon): the escalation entry is only visible to users allowed to see private followups.

On **Escalate**:

1. The target group **replaces** all the groups assigned to the item.
2. The assigned technicians are removed, if *Remove technician after escalation* is enabled.
3. The status is changed, if a status after escalation is configured.
4. An escalation entry is added to the timeline: source groups → target group, author, date and comment.

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-21a9bdc54c941988ff695a1c52117df6ca7bdd19%2Fmoreoptions_timeline_escalation.png?alt=media" alt="Escalation entry in the timeline"><figcaption></figcaption></figure></div>

An escalation is refused, with an explicit message, when the group no longer exists, can no longer be assigned, is not visible from the entity of the item, or is already assigned.

### Escalation history

Once an item has been escalated, a **history** button appears next to *Escalate*. It lists the escalations of the item, most recent first. The button on each line escalates the item again to the same group, when possible (its tooltip explains why otherwise). Users who cannot assign the item still see the history.

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-c128e9e11211bf67b7e35dfbcf2cad0f2f12c69f%2Fmoreoptions_escalation_history.png?alt=media" alt="Escalation history"><figcaption></figcaption></figure></div>

### Escalate to group rule action

The business rules for **tickets**, **changes** and **problems** get a new action: **Assign — Escalate to group**. Unlike the core *Technician group* action, it escalates the item: it goes through the same process as a manual escalation (the group replaces the assigned ones, technician removal, status change, timeline entry with the comment *"Escalated by a business rule."*).

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-5e40c120f975db9d23b158a30b0f744397403f97%2Fmoreoptions_rule_action.png?alt=media" alt="Escalate to group action in a ticket business rule"><figcaption></figcaption></figure></div>

* The escalation must be enabled for the entity of the item.
* When the escalation is not possible (escalation disabled, group not assignable…), nothing is changed and the reason is written in the GLPI events log (**Administration > Logs**), since rules can run without a user, from the mail collector for instance.
* The action can only come from the rules: this field sent by a form or the API is ignored.

**Check rules page.** The **Check rules** button of the *Escalate* tab opens a page that lists all the *Assign* actions on a technician group in the rules the user can see. For each one, the field can be switched between **Technician group** and **Escalate to group**, then saved. Only the rules the user is allowed to update can be changed.

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-e89bac686c7d0b277dcb58f7a7be79fa5c186ac0%2Fmoreoptions_rules_review.png?alt=media" alt="Check rules page"><figcaption></figcaption></figure></div>

***

## Escalate filter tab

### Group filter

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-caa8bf69809962ee4e6eeb8cadf9f076b49800cf%2Fmoreoptions_config_escalate_filter.png?alt=media" alt="Group filter settings"><figcaption></figcaption></figure></div>

| Option                                    | Values                                            |
| ----------------------------------------- | ------------------------------------------------- |
| **Activate group filter**                 | No / Yes                                          |
| **Profiles allowed to bypass the filter** | List of profiles (or *Inherit* on a child entity) |

When the group filter is active, an item can only be escalated to the **next level** of the escalation tree below: the groups that the groups currently assigned to the item escalate to, in the entity of the item. For instance, a ticket assigned to *N1 - Support* can only be escalated to *N2 - Network* or *N2 - Systems*:

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-0dcee840f29e97ce556b1deaa2a1941ee7fb701b%2Fescalate-form-group-filter.png?alt=media" alt="Escalation form restricted by the group filter"><figcaption></figcaption></figure></div>

* The filter applies to the **Escalate** form, to the *escalate again* buttons of the history (greyed out, with the reason in their tooltip) and to the server-side check of every escalation, including the **Escalate to group** rule action: a rule escalating to a group outside the next level is refused and logged.
* When no group is assigned to the item, there is no level to start from: every group can be chosen.
* The profiles selected in **Profiles allowed to bypass the filter** can escalate to any group.

### Escalation tree

The escalation tree defines, for an entity, which groups each group escalates to. It is edited as a graph below the group filter.

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-930110ae6388fbc72d24fe46ceb05900790d00f0%2Fmoreoptions_tree_root.png?alt=media" alt="Escalation tree of the root entity"><figcaption></figcaption></figure></div>

**Reading the graph**

* Each box is a group; its badge (**L1**, **L2**, **L3**…) is its level in the escalation. A group no other group escalates to is a first level.
* Each arrow is a link "escalates to".
* The panel on the right lists the groups **In the graph** and the groups **To place**: the groups that can be assigned in the entity (groups of the entity, or recursive groups of a parent entity).
* The footer counts the groups and the links.

**Link types**

| Type                            | Arrow       | Where the link applies                                               |
| ------------------------------- | ----------- | -------------------------------------------------------------------- |
| **Basic**                       | solid, dark | Only in the entity where it was created.                             |
| **Inherited**                   | solid, blue | In the entity and all its child entities.                            |
| Replicated from a parent entity | dashed      | An *Inherited* link of a parent entity, as seen from a child entity. |

In a child entity, the links inherited from the parent entities are shown dashed. Deleting one there removes it from this entity and its own child entities only.

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-bf74d0b708438eeca7ddd0f6c352cf24c9748051%2Fmoreoptions_tree_child.png?alt=media" alt="Escalation tree of a child entity, with links inherited from the root entity"><figcaption></figcaption></figure></div>

**Editing the graph** (requires the *Update* right on the configuration)

* Drag a group from the list onto the graph, or click it, to place it.
* Drag a group onto another group to link them. The type of the new link is the one selected in the toolbar (*Basic* or *Inherited*).
* Right-click a group or a link for more actions: add a group escalating to it or to escalate to, change the link type, delete the link, remove the group from the graph.
* Keyboard: **Delete** removes the selection, **Ctrl+Z / Ctrl+Y** undo / redo, **Escape** closes the selection.
* Drag the background to move around, scroll to zoom.
* Toolbar: undo / redo, **orientation** (horizontal or vertical), **fit the graph to the view**, and **remove all the links** (in a child entity: removes the links of this entity and restores the inherited ones).

Click **Save** below the tree to save it; the same button also saves the settings of the tab.

**Consistency checks on save**

* **Loops are refused:** a group cannot escalate, directly or not, to itself. This is checked in the entity and in all its child entities, since an inherited link and a link of a child entity could form a loop together.
* If someone else saved the tree of the entity in the meantime, the graph is reloaded and the unsaved changes are discarded.
* When a group or an entity is purged, its links are deleted.

***

## Migrating from the Escalade plugin

From GLPI 12, the Escalade plugin reaches its end of life: its escalation features are provided by MoreOptions 1.1. Its last version, **Escalade (End Of Life)**, no longer does anything on tickets; it only keeps the Escalade data so that its **group filter** can be migrated to MoreOptions.

### Steps

1. Update Escalade to its End Of Life version, and keep it enabled.
2. Install and enable MoreOptions 1.1 (or later).
3. Check the data to migrate, then simulate and run the migration, from the interface or from the command line.
4. Check the result in MoreOptions (see below), then uninstall Escalade.

### End Of Life page

The *Configure* button of Escalade in **Setup > Plugins** opens its End Of Life page, with a link to the migration status.

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-8cba611dc28999bddb1845b0499194e935517642%2Fescalade-eol-info.png?alt=media" alt="Escalade End Of Life page"><figcaption></figcaption></figure></div>

### Migration status

The migration status page shows:

* whether the group filter of Escalade is active;
* the number of links already migrated to MoreOptions;
* the number of users allowed to bypass the filter in Escalade;
* every Escalade link (source group → destination group) with its status: *Migrated* when MoreOptions has a link between the same groups in the root entity.

A red banner is shown, and the buttons are disabled, while MoreOptions is not enabled.

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-760e33eabcfa9ce4bd502a08f8121b9d3ccc1135%2Fescalade-migration-status-before.png?alt=media" alt="Migration status before the migration"><figcaption></figcaption></figure></div>

### Running the migration

**From the interface**, in the *How to Migrate* card of the migration status page (requires the *Update* right on the setup):

* **Simulate** runs the whole migration, then rolls it back: nothing is changed. The result is shown as messages: warnings for the data that cannot be migrated, then a summary.
* **Migrate** runs it for real, after a confirmation.

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-38a2129bfb6e1f56502dbae113663ec2684aabe0%2Fescalade-migration-simulate.png?alt=media" alt="Result of a simulation"><figcaption></figcaption></figure></div>

**From the command line**, from the GLPI root directory:

```bash
# Simulation: nothing is changed
php bin/console plugins:moreoptions:migrate_escalade --dry-run

# Migration
php bin/console plugins:moreoptions:migrate_escalade
```

Both run the same migration, in a single transaction: if an error occurs, nothing is changed. The migration can be run again: what is already migrated is kept.

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-60ea8f46f5ff7ca1259e1b260e5222227f7f1699%2Fescalade-migration-status-after.png?alt=media" alt="Migration status after the migration"><figcaption></figcaption></figure></div>

### What is migrated

| Escalade                                                           | MoreOptions                                                                                                                                                              |
| ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Groups a group can escalate to (**Escalation** tab of the groups)  | **Inherited** links of the escalation tree of the **root entity**: as in Escalade, they apply in every entity where both groups can be assigned.                         |
| **Enable filtering on the groups assignment** option, when enabled | **Activate group filter** set to *Yes* in the root entity, inherited by the child entities. A disabled filter changes nothing.                                           |
| Users allowed to bypass the filter                                 | **Not migrated**: MoreOptions allows **profiles** to bypass the filter. A warning gives the number of users concerned; choose the profiles in the *Escalate filter* tab. |

Some links are **ignored**, with a warning:

* a link from a group to itself;
* a link to or from a group that no longer exists.

Duplicate links are migrated once, and a link that MoreOptions already has between the same groups in the root entity is **kept as it is** (it may have been changed since in MoreOptions). A link involving a group that cannot be assigned is migrated, but never applies, as in Escalade.

### Checking the result

After the migration, the links appear in the **Escalate filter** tab of the root entity, as *Inherited* links (solid blue arrows):

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-3b398ddf06f31a6d6eaf2f3a8b841f9e802fa7d7%2Fescalade-migrated-tree-root.png?alt=media" alt="Escalation tree of the root entity after the migration"><figcaption></figcaption></figure></div>

In a child entity, they are replicated (dashed arrows), with the links of the groups of this entity, here *N1 - Paris desk → N2 - Systems*. The group filter inherits the value of the root entity:

<div align="left"><figure><img src="https://3573604317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUCcURk2xlvtpVGbiRZf%2Fuploads%2Fgit-blob-9dc5b773445daa1c134661fd90a02be218860eb9%2Fescalade-migrated-tree-child.png?alt=media" alt="Escalation tree of a child entity after the migration"><figcaption></figcaption></figure></div>

The migrated links can then be changed like any other link: turned into *Basic* links, removed from a child entity, etc.

***

## Uninstallation

Uninstalling the plugin from **Setup > Plugins**:

* deletes its tables: configurations, escalation history and escalation tree;
* switches every **Escalate to group** rule action back to the core **Technician group** action, so that the rules keep assigning a group.

***

## Summary of features

| Feature                                            | Ticket | Change | Problem |
| -------------------------------------------------- | :----: | :----: | :-----: |
| Groups of associated item / requester / technician |    ✅   |    ✅   |    ✅    |
| Technical manager / group of the category          |    ✅   |    ✅   |    ✅    |
| Technician from task to parent item                |    ✅   |    ✅   |    ✅    |
| Prevent closure with To Do tasks                   |    ✅   |    ✅   |    ✅    |
| Mandatory fields to solve and close                |    ✅   |    ✅   |    ✅    |
| Mandatory task fields                              |    ✅   |    ✅   |    ✅    |
| Manual escalation and history                      |    ✅   |    ✅   |    ✅    |
| *Escalate to group* rule action                    |    ✅   |    ✅   |    ✅    |

***

## FAQ

If you have any questions about using the plugin, please consult our FAQ

<a href="https://help.glpi-project.org/faq/plugins/more-options.md" class="button secondary">Go to FAQ</a>


---

# 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/doc-plugins/plugins-glpi/more_options.md?ask=<question>&goal=<user_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.
