Agreed - there should checkbox if person who did update should receive feedback about it or not. In notification list there could be number of contacts (including EMCs one so your tech should add themselves even there should be automatic procedure for that when owner is assigned and changed).

There might be a problem with implementation of this as there might be cases where SR has persons A, B and C on the list and D from the same company does update. If primary contact is selected not to receive own updates and if software is configured in such way - primary contact won't be aware of update. However if focus is on person who did update (in this case D) then that should not be a problem (unless person D wants that update, but setting by primary contact is prohibiting that). Nevertheless, I would like to see the change in that direction.

Now that you mention, I recently had 2 SRs opened and I can't say I did get notifications when SR was updated and closed. I only did get notification that SR has been opened after several hours from doing it and only for one SR. It seems that this works sometimes and sometimes not. However, since there at least 2 mail queues involved and possible spam filters too I didn't do fully investigation for that matter as I tend to check SRs manually anyway.

Hello,

First, we do send notifications to the service request owner (when there is one) when an update happens via Powerlink. We have not heard of this not working to date but I will look into it for you.

In regards to the item on notifying your self, I will capture this as an enhancement request. We currently do not have the system designed to understand who is providing the update, just send the notification on update. This is a good idea and I will get it logged for you.

Regards

Jay Leclerc

Hi Hrvoje,

I think that you get notification email of the SR creation but to get the update notifications you have to enable send notification when case is updated. That can be set in each case individually or be preset in your preferences.

/Nils-Erik

That's what I do usually and obviously it does not work very well in my case.

Today my collegue had duplicate sent once - same message and different message ids. If someone wants to check ids are 3542079 and 3542080.