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
  • Create the pending reason
  • Setting up the dunning option
  • Setting up the resolution option
  • Define a follow-up template
  • Define a solution template
  • Adding a reason for pending to a ticket
  • Automatics actions

Was this helpful?

Edit on GitHub
Export as PDF
  1. Helpdesk

Add a pending reason

PreviousManaging problemsNextCreating Templates for Tickets

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


A reason to wait allows you to put a ticket on hold, send automatic reminders and resolve the ticket if it has not received a response. All these actions are subject to conditions:

  • the interval between automatic follow-ups,

  • the number of follow-ups before resolution,

  • setting up a follow-up template,

  • implementation of a solution template.

Create the pending reason

Go to setup > dropdowns and enter pending reasons in the search box.

Click on add

Name your pending reason

Setting up the dunning option

What happens next will depend on your needs. Start by defining the automatic follow-up frequency. In our example, we're going to carry out every 3 days.

Setting up the resolution option

We're going to define that a ticket can be closed after 3 follow-ups.

Define a follow-up template

This template will be used to send out reminders. Click at the end of the follow-up template field

Name your template and indicate the source of the tracking (helpdesk in our case)

Then enter the content of your follow-up, which will be sent to your contact person

Add this follow-up and then select it from the drop-down list

Define a solution template

When this template is added to the ticket, it will close the ticket.Repeat the same process as for the follow-up templateClick on the at the end of the solution template field

Name your templateSelect the solution incident option so that the ticket can obtain the resolved statusAdd your follow-up and select it from the drop-down list.

Your pending reason is now ready, all you have to do is click on add

Adding a reason for pending to a ticket

When you respond to a ticket, you'll be able to click on the pause symbol and select the pending reason you've just created

Automatics actions

Warning

Pending reasons depend on the pendingreason_autobump_autosolve automatic action. Check that this is active and correctly set (setup > automatic actions)

Alt text
Alt text
Alt text
Alt text
Alt text
Alt text
Alt text
Alt text