Debugging ticket rules in GLPI is a task that consumes time and requires deep knowledge of the environment configuration. – The Rule Inspector module exposes, directly in the ticket tab, which rules were applied and which did not pass the criteria – without needing to open each rule manually.
The problem
Ticket rules are one of GLPI's most powerful features: they assign technicians, define SLAs, categorize tickets, and trigger notifications automatically. But when something doesn't work as expected – a ticket that wasn't assigned, a category that wasn't set – the diagnosis is painful.
The administrator needs to open the rule manager, examine each rule one by one, verify criteria, check execution order, and try to mentally reconstruct what happened when that ticket came in. In environments with dozens or hundreds of rules, this can take hours.
Rule Inspector inverts this logic: instead of going to the rules, the rules come to you, organized and presented in the context of the ticket you're analyzing.
How Rule Inspector works
After installing and activating the module, a Rules tab appears in each GLPI ticket. From there:
- Query rules – One click evaluates all active ticket rules in the ticket's entity. The result shows which rules were applied, which matched but were not executed, and which did not pass the criteria – all with evaluated criteria details.
- Query persistence – The query result is saved per ticket. When reopening the ticket, the button changes to "Redo query", indicating that a previous evaluation is already available.
- Test by ID – On the module's standalone page, the Test tab allows entering any ticket ID and seeing which rules are true for it, without needing to open the ticket.
- Filtered history – The History tab lists all executed evaluations, filtered by entities accessible to the user. There is no information leakage between different entities.
- CSV export – History can be exported in CSV, including a detailed criteria column in
criteria | condition | valueformat, useful for auditing and reports.
The module evaluates up to 1000 rules per query (ordered by ranking), with a visual indicator when the limit is reached.
How to activate
- Install the NexTool plugin on GLPI
- Go to Setup > NexTool > Modules
- Activate the Rule Inspector module
- Synchronize permissions via the NexTool panel so profiles have access to the tab
Who is it for
Rule Inspector is designed for GLPI administrators and configuration analysts who need to ensure ticket rules are working correctly. Typical scenarios:
- Administrator who needs to validate whether a new rule is being applied correctly after configuration
- Quality analyst auditing consistency of automatic ticket assignments
- Service desk manager investigating why certain tickets are not receiving the correct category or SLA
- Teams that went through a GLPI version migration and need to validate whether rules continue working as expected
Compatibility
- GLPI: 10.x and 11.x
- Plan: FREE
- Plugin: NexTool 3.x+
Next step
Rule Inspector is part of NexTool, a modular plugin for GLPI. Explore all available modules or contact the team for a demonstration.
This content was produced with the assistance of artificial intelligence and reviewed by the Nextool Solutions team. Screenshots are from the real GLPI environment with the NexTool plugin.
