Problem Flow
Automated ITIL Problem Management in GLPI
Problem Flow brings ITIL Problem Management to GLPI automatically. It watches solved and closed tickets with rules in the same format as GLPI's business rules: category, location, associated item type, solution type, priority, request source, groups, requester and words in the title, the description or the solution text. When the minimum number of tickets is reached within the period, the module opens the Problem and links the tickets that caused it.
Features
It ships with 27 ready-made rules, inactive, for the most common cases: the same device failing again and again; Wi-Fi, printing, power or telephony issues at the same location; services such as email, VPN, login, backup and digital certificates; recurring workarounds; and every critical incident. The Test button shows what the rule would have caught in your tickets, without creating anything, and you turn on only what makes sense.
Counting can be split by item, location, category, technician group, requester or department: with a minimum of 5, five Wi-Fi incidents at the Downtown branch and five at the North branch open two Problems, one per branch. A minimum number of distinct requesters keeps a single person from raising the alarm, and a minimum interval prevents repeated Problems. The rule's actions define how the Problem is created: title, template, category, urgency, impact, technician group, technician and observer group. Root cause analysis follows GLPI's normal flow, and the Logs tab shows which rule opened each Problem, for which group and with which tickets.
How it works
Pick a template or create the rule
In the Rules tab, start from one of the 27 ready-made templates or create your own: criteria, how many tickets in how many days, how to group and how the Problem should be opened.
Test before turning it on
The Test button simulates the rule over the period, with your tickets: it shows each group, how many tickets and requesters it added up against the minimum, and a preview of the Problem. Nothing is created.
Automatic evaluation
Whenever a ticket is solved or closed, and also through GLPI's automatic action (every 6 hours by default), the active rules are evaluated. When the minimum is reached, the Problem is opened with the tickets linked.
Root cause analysis in GLPI
The Problem gathers the incidents for root cause analysis in GLPI's normal flow. The Logs tab shows which rule opened each Problem, for which group and with which tickets.
See it in action
A quick tour of what the plugin does in practice.
Image gallery
Screenshots for this section are coming soon.
Start using Problem Flow
View available plans or read the full article about this module.