You are not logged in.
Pages: 1
Possibly a bug, possibly a feature:
If a watcher is defined by email address instead of picking a user from the "known" list, that email address isn't matched back to known users
The result is that the watcher does not get URLs in notifications and if he logs in using his account, does not see the tickets that he's supposed to be watching.
As soon as the email address is replaced with the GLPI user ID, things work as expected.
(It took a while to work out why this was happening..)
Offline
Are yours users automaticuly synchtonized with a ldap server?
CentOS 6.5 - CentOS 7.x
PHP 5.6 - PHP 7.x - MySQL 5.6 - MariaDB 10.2 + APC + oOPcache
GLPI from 0.72 to dev version
Certifiée ITIL (ITV2F, ITILF, ITILOSA)
Offline
Yes they are, for local UID and email addresses (departmental)
However they have also adding other email addresses (their institutional address and/or offsite contacts such as gmail) in their personal profile settings.
Offline
if you use only email user, you can't have this email back to know users because you don't know he (a first name and a name is not enough for multi users with same name and firstname)
Email user is for user doesn't know in GLPI, so user that can't log in GLPI, so URL is not set.
CentOS 6.5 - CentOS 7.x
PHP 5.6 - PHP 7.x - MySQL 5.6 - MariaDB 10.2 + APC + oOPcache
GLPI from 0.72 to dev version
Certifiée ITIL (ITV2F, ITILF, ITILOSA)
Offline
_I_ know what it's for. The problem is that users don't and even if we train the existing ones, some will not listen - plus there are a steady stream of new arrivals, etc.
The problem exists when people add an email address for "watcher" in the ticket instead of using the "people selector"
It would be "extremely useful" if GLPI attempted to match email addresses against the user database (in addition to the existing matching routines) for the watcher fields - this would save us having to deal with repeatedly filed reports of "GLPI won't let me see a ticket I'm watcher on"
Offline
I've just discovered why people are entering email addresses.
When they select a watcher in self-service, only a limited list of users is presented (technicians, or in some cases, nothing at all)
Is there a setting for allowing self-service submitters to have wider selection of watchers?
Offline
Additional request: We need watchers to be able to post to the tickets (or allow users to set multiple "requestors")
Offline
I've just discovered why people are entering email addresses.
When they select a watcher in self-service, only a limited list of users is presented (technicians, or in some cases, nothing at all)
Is there a setting for allowing self-service submitters to have wider selection of watchers?
In self-service users in the dropdown are user of groups of the creator of the ticket
CentOS 6.5 - CentOS 7.x
PHP 5.6 - PHP 7.x - MySQL 5.6 - MariaDB 10.2 + APC + oOPcache
GLPI from 0.72 to dev version
Certifiée ITIL (ITV2F, ITILF, ITILOSA)
Offline
_I_ know what it's for. The problem is that users don't and even if we train the existing ones, some will not listen - plus there are a steady stream of new arrivals, etc.
The problem exists when people add an email address for "watcher" in the ticket instead of using the "people selector"
It would be "extremely useful" if GLPI attempted to match email addresses against the user database (in addition to the existing matching routines) for the watcher fields - this would save us having to deal with repeatedly filed reports of "GLPI won't let me see a ticket I'm watcher on"
email field is used if you want, only for this ticket, send the notification to another address mail
CentOS 6.5 - CentOS 7.x
PHP 5.6 - PHP 7.x - MySQL 5.6 - MariaDB 10.2 + APC + oOPcache
GLPI from 0.72 to dev version
Certifiée ITIL (ITV2F, ITILF, ITILOSA)
Offline
Additional request: We need watchers to be able to post to the tickets (or allow users to set multiple "requestors")
Watcher can only watch the ticket.
If you want that he can do action, it must be requestor of the ticket
CentOS 6.5 - CentOS 7.x
PHP 5.6 - PHP 7.x - MySQL 5.6 - MariaDB 10.2 + APC + oOPcache
GLPI from 0.72 to dev version
Certifiée ITIL (ITV2F, ITILF, ITILOSA)
Offline
email field is used if you want, only for this ticket, send the notification to another address mail
People are using the watcher field to add other affected individuals, because they cannot add them as requestors.
The problem is that in the watcher dropdown menu either _no_ users appear or only the helpdesk technicians, so they are entering the email address of the people they want to monitor the ticket.
Offline
Pages: 1