Ah that's good news about additional emails. One problem we have had , is we import users from Active Directory. However not all users in our AD have the email attribute set. When it is set in GLPI (manually) , if they log into GLPI, and their AD information is synced, it over writes the change made in GLPI's DB and removes their email address. If this new additional email addresses field would be a way to resolve that, then that's 2 problems solved for me.
- Trey On Wed, Jul 27, 2011 at 3:22 AM, MoYo <m...@indepnet.net> wrote: > ** > Le 27/07/2011 10:18, Trey Dockendorf a écrit : > > The problem we are having is if the user's email is under "Requester" , and > they send in follow-ups it creates a new ticket that is linked to the > original. > > > yes this bug have been fixed. > > > These user's aren't in the GLPI DB so only their email address shows up. > We also have some situations where a user will reply with an email address > that differs from the one in GLPI's DB, in which case it will again create a > new ticket rather than adding the response as a follow-up. For my > organization all mail goes to u...@tamu.edu, but if they respond from the > web based mail it will show up as from u...@neo.tamu.edu, which > complicates things. I hope that made sense. > > > Yes it is a real problem. In 0.83, a solution will be to define several > emails per users but it will not solved all troubles. > So, I think your patch is interesting. > > Regards > > Julien > > > > _______________________________________________ > Glpi-dev mailing list > Glpi-dev@gna.org > https://mail.gna.org/listinfo/glpi-dev > >
_______________________________________________ Glpi-dev mailing list Glpi-dev@gna.org https://mail.gna.org/listinfo/glpi-dev
