Ticket Flow

One ticket opens the next one, on its own, in GLPI

Ticket Flow takes off your team's memory the work that always comes with another piece of work. When a ticket in a category is created, solved or closed, the module opens a new ticket from a GLPI ticket template. When a service request is opened, the financial approval request is opened with it; when a maintenance ticket is solved, the quality survey opens on its own.

LicensedGLPI 11 and 12

Features

The new ticket is linked to the source ticket from the start and inherits its requester, requester group and location. The source ticket receives a follow-up with the link to the generated ticket. The template has the final word: inheritance only fills what the template left blank, and each inheritance can be turned off in the flow.

A category can have several flows, run in the order you define. Each flow applies to one entity, with the option to apply to child entities too, and the Logs tab records every run with the source ticket, the generated ticket and the result. If a flow fails, the original ticket is created normally, the other flows keep running and the error is recorded.

Triggered by a ticket event: created, solved or closed, in each category

Uses GLPI's native ticket templates

Several flows in the same category, with an execution order

Flows per entity, with the option to apply to child entities

Generated ticket linked to the source ticket, inheriting requester, group and location

Follow-up on the source ticket with the link to the generated ticket

Logs tab with every run, with filters and sorting

Separate permissions to view flows, view settings, run the test and view diagnostics

Enable and disable flows without deleting them

How it works

Step 1

Prepare the ticket template

Build the ticket template in GLPI with the fields the new ticket should have, such as title, description, category, group and priority.

Step 2

Create the flow

Choose the category, the event (ticket created, solved or closed), the template, the entity, the execution order and what the new ticket inherits from the source ticket.

Step 3

Activate

With the module active, each active flow runs on its own at every event. A flow can be turned off without being deleted, and the Test tab opens a real ticket from a template to validate the setup.

Step 4

Follow up in the Logs tab

Every run is recorded with the source ticket, the generated ticket and the result, with filters and sorting.

See it in action

A quick tour of what the plugin does in practice.

Video demo coming soon.

Image gallery

Start using Ticket Flow

View available plans or read the full article about this module.

View plans Read full article
Need help?