You are not logged in.
I have not clear the difference between them, or the purpose for what they are expected to be used.
Problems can contain tickets, but what are they designed to do?
Offline
Ticket, (Incident or Service request) and Problem are different ITIL processus.
Main difference for problem
- multi entities
- multi items
- multi incidents
Dév. Fedora 29 - PHP 5.6/7.0/7.1/7.2/7.3/7.4 - MariaDB 10.3 - GLPI master
Certifié ITILv3 - RPM pour Fedora, RHEL et CentOS sur https://blog.remirepo.net/
Offline
Good. After your answer i have been reading about some itil concepts to use glpi the right way.
So, extending the question, would be good practice to work like this?
itil concept ----> support in glpi
incident --> ticket incident type
request --> ticket request type
problem --> problem
know error --> knowledge base or recurrent tickets?
Also, how would you recommend to work with change management processes. Should i use tickets to do this.
I know i lack some important itil concepts. I am trying to start using glpi making at least the biggest decisions of good practices
Offline
Known error => solution template ?
Change management will be a new feature of next major version.
Dév. Fedora 29 - PHP 5.6/7.0/7.1/7.2/7.3/7.4 - MariaDB 10.3 - GLPI master
Certifié ITILv3 - RPM pour Fedora, RHEL et CentOS sur https://blog.remirepo.net/
Offline
so (this is the last one, I promise!)
what is the intended use for recurrent tickets ?
Offline