LogoLogo
DownloadGLPI ChangelogPricesGLPI Webiste45-day free trial
  • Welcome
  • FAQ
  • FAQ Plugins
  • Tutorials
  • Videos
  • Most popular
    • Setting up Oauth IMAP Entra
    • Customise my logo
    • Setting up Oauth SMTP Entra
  • Account and subscription
    • Subscribe to GLPI cloud
  • Authentication
    • Activate sso
    • Authenticate with local LDAP
    • Integrate GLPI Network Cloud and LDAPS (Entra)
    • Setting up LDAP
  • Automatic actions
    • Setting up automatic actions
    • Check automatic actions
  • General
    • Setting up your calendar
    • Managing dashboards
    • Fields unicity
  • Helpdesk
    • Add a task
    • Add changes
    • Creating ITIL Category
    • Add an external planning
    • Managing problems
    • Add a pending reason
    • Creating Templates for Tickets
    • Using survey satisfaction
    • Setting up Service levels (SLA)
  • Inventory
    • Using blacklist
    • Collect Data
    • Inventory Android smartphones
    • Computer inventory
    • Deploying agents via GPO
    • Deploy via GlpiInventory
    • Using impact analysis
    • Installing the GLPI agent Toolbox
    • Setting up mirror servers
    • Setting up remote inventory
    • Securing exchanges between GLPI agents <-> GLPI server
    • Inventory printers and network hardware
  • Knowledge
    • Overview
    • Search engine
  • My instance
    • Customise my logo
    • Final migration
    • Export local database
    • Export my data
    • Find out my address
    • Migrate my existing GLPI on GLPI Network Cloud
    • Privacy policy and GPRD
    • Rename my instance
    • Slowdown on my instance
  • Notifications
    • Setting up Oauth SMTP Entra
    • Oauth SMTP Google
    • Setup notifications
    • Reminders
  • Plugins
    • Install and update plugins
    • Marketplace
  • Procedures
    • Apply patch
    • Free up space on your database
    • Install GLPI on Ubuntu
    • Use Percona's tools for large GLPI databases
    • Registration key marketplace
  • Receivers
    • Setting up OAuth IMAP Google
    • Setting up receiver and tickets
    • Collect emails from Gmail
    • Setting up Oauth IMAP Entra
    • Receiver iCloud
    • Receiver and delegating mailboxes
    • Receiver Office365
  • Rules
    • Authorizations rules
    • Business rules for tickets
    • Rules engine and dictionaries
  • Tools
    • Manage your projects
    • rssfeed
Powered by GitBook
On this page
  • Rules
  • Create a new rule
  • Setting up the criteria for your business rule
  • Setting up actions for your business rule
  • References

Was this helpful?

Edit on GitHub
Export as PDF
  1. Rules

Business rules for tickets

PreviousAuthorizations rulesNextRules engine and dictionaries

Last updated 2 months ago

Was this helpful?

LogoLogo

Social Media

  • GitHub
  • Instagram
  • LinkedIn
  • Facebook
  • Youtube
  • X
  • Reddit
  • Telegram

Category

  • FAQ
  • FAQ Plugins
  • Tutorials
  • Videos

Ressources

  • Download
  • GLPI Changelog
  • Prices
  • GLPI Website
  • 45-day free trial

©2025 - Teclib

Business rules for tickets are predefined conditions and actions that automate processes, ensuring that tickets are categorized, assigned, and processes efficiently. By defining these rules, teams can reduce manual work, improve response times, and ensure compliance with service level agreements (SLAs).

The rules are accessible from the Administration > Rules > Business rules for tickets menu.

Setting up Business Rules involves 4 main stages:

  1. Creating a new rule.

  2. Defining the criteria which will match all or some conditions, according to the logical operator.

  3. Defining the desired actions once the criteria matches.

  4. Defininig the order of execution of this rule.

Rules

A rule is made up of different criteria. Depending on the option chosen (OR / AND) one or all of the criteria must be completed to trigger an action list.

Create a new rule

  • Administration > Rules > Business rules for tickets click on Add,

  • Name your rule,

  • In Use rule for you choose if the rule runs just when a ticket is created, when it is updated or both. In this example we a re using just for Add,

Reminder

Every rule created start running in tickets opened or updated after the rules creation. So previous tickets will not reveive any actions from new rules created or updated.Give your rule a Description to make it easier to read without the need of opening criteria and actions,

  • Add additional Comments to your rule if you need,

  • Set Active to Yes if you want the rule to be activated right after its creation,

  • Click on Add at the end of the form.

Example

We are creating a rule to set our SLA and OLA according to this article:

  • Every time a ticket is opened from the Entity called Brazil AND the Category is not Servers

  • The ticket must assume A Time to Own of 4 hours in Brazil and a Time to Resolve of 5 days in Brazil

These SLAs must be already created.

Reminder

This is just ONE example. You may create other rules according to your business.

Setting up the criteria for your business rule

  • In your new business rule, click on the tab with the name Criteria,

  • Click on Add a new criterion,

  • Chosse a Criterion that matches one or more needs of your tickets,

  • In this case Criterion > Entitiy > is > Brazil

  • Click on Add,

  • Choose the second Criterion > Category > is not > Servers

  • Click on Add.

Reminder

Since we have chosen the Logical operator **`AND`**, the rule will execute its action only when all the criteria match.

Setting up actions for your business rule

  • In your new business rule, click on the tab with the name Actions,

  • Click on Add a new action,

  • Chosse an Action that matches one or more needs of your tickets,

  • In this case Action > SLA Time to own > Assign > TTO - 4 hours in Brazil

  • Click on Add,

  • Choose the second Action > SLA Time to resolve > Assign > TTR - 5 Days in Brazil

  • Click on Add.

Reminder

If for some reason, once a rule matches, the engine needs to stop running the next rules, you must choose the Action > Skip remaining rules so no other rule after that one in the order will be executed.

References

Documentation GLPI "Rules"

You can refer to general behavior of rules .

Choose the Logical operator according to your needs - if you are not sure which one to use, see more . In this example we are using the Logical operator AND ,

BUSINESS RULES
CREATE RULE
ADD CRITERIA
ADD ACTIONS
SKIP RULES
here
here