Hi,
We raised an enhancement request about a year ago regarding the fact that when you create an escalation notification and select to send to 'assignee', it was sending to the whole group and not just the one assignee user. I've seen the other discussion threads related to this - 'All Group members receiving all group messages' and 'Assignment Notifications going to all Group members' - and the TPS.CONFIG suggested fix does not work, at least on 7.2.6 anyway, as we modified the files about 6 months ago and the problem still exists.
This property seems to use the term 'assignee' to focus on sending the notifications to the 'assigned group' rather than the 'assigned user'. I will shortly be contacting support about it, but wanted to put a discussion in before doing so.
We are on LANDesk 7.2.6 and had delayed going live with email in the hope that this issue would have been resolved by now although I cannot find any evidence to suggest yet that this is the case. We switched on mail last week and the only outstanding problem now really is that SLA notifications are being sent to entire support groups regardless of whether the Incident or Change is assigned directly to one person in that group or not. It is therefore quite an inconvenience and distraction for other team members when they are constantly being sent notifications for workloads that are with other members of their team. Much customer correspondence is done via email, and inboxes are regularly getting hit with irrelevant messages, thus reducing their value.
What would be ideal is that in the response level escalation actions, you could specify the notification recipients 'assignee group' or 'assignee user' from the dropdown.
As mentioned, we have modified every TPS.config file in use to have the additional key <add key="AssignmentNotificationsToUserOnly" value="true" /> - performed IIS resets, and the same behaviour is exhibited. Does anyone know how to fix this, and if not any awareness that iof it being resolved in 7.3?
Thanks,
Eamonn