Support Forum

[PavelKolarik]

We have installed TS40b18 and the behaviour of notifications seems to be changed slightly. For example I have defined two notification rules - the first one sends the notification to the task's assignee while another rule (basically the same) notifies the task's submitter. Prior to beta18, when I were both the task's submitter and assignee I received two notifications. Now I've received just one. In the case of another task I fit even three notification rules and again got just one notification. Is it a new feature or a bug?

If it is a feature I agree it is quite usefull not to get more than one notification. But in this case I would suggest to add a "priority" field to the notofication rules in order me to be able to define the order the rules are evaluated in.

[admin]

We have installed TS40b18 and the behaviour of notifications seems to be changed slightly. For example I have defined two notification rules - the first one sends the notification to the task's assignee while another rule (basically the same) notifies the task's submitter. Prior to beta18, when I were both the task's submitter and assignee I received two notifications. Now I've received just one. In the case of another task I fit even three notification rules and again got just one notification. Is it a new feature or a bug?

This is a feature. Actually, sending multiple e-mail notifications per event was a bug.

If it is a feature I agree it is quite usefull not to get more than one notification. But in this case I would suggest to add a "priority" field to the notofication rules in order me to be able to define the order the rules are evaluated in.

This is not possible to do now - change change require DB modification, too late for it

But what is the reason to be notified by some specific rule only ?

[PavelKolarik]

But what is the reason to be notified by some specific rule only ?

We use different email templates for different rules. The templates differ slightly e.g. in Subject which allows our users to define rules in their email clients in order move the notifications into specific email folders. For example, a guy with the role of team leader receive notification about all the changes in a project he leads (in order to have an overview). In parallel, everybody receives the update notifications about the tasks where one is the assignee. Of course, assignee's notifications are more important than the team leader's ones so that they are moved to another email folder automatically. Now we do not know which notification rule will aply first and it may happen that the assignee's notification will not come.

BTW, it seems there is some bug in the current behaviour too. A colleague of me has received two notifications on the same event. In this case notifications have been generated by different rules and the rules use the same email template. I guess there are two possible reasons why it happened:
1) The two rules are not defined on the same task (folder)
2) The first rule is defined for a role while the second one is defined for the particular user

[admin]

OK, we'll check what we can do there.

[Petr]

BTW, it seems there is some bug in the current behaviour too. A colleague of me has received two notifications on the same event. In this case notifications have been generated by different rules and the rules use the same email template. I guess there are two possible reasons why it happened:
1) The two rules are not defined on the same task (folder)
2) The first rule is defined for a role while the second one is defined for the particular user

I've checked - all works fine. I've created two email notifications.
I have user with login - Admin, role - administrator.
First notification: for user - admin.
Second notification: for role - administrator.
Still recieve one notification.
Please send anonymous database + how to replicate.

[PavelKolarik]

Please send anonymous database + how to replicate.

Hi Petr, I have tried to replicate the double notification but I have not succeeded, maybe because we have switched to newer 4.0 beta19 since that time. Nevermind - let's consider it as solved.