|
|
|
See related issue JRA-2644. Following up on Anton's comments, JIRA is set up so that an administrator decides what notifications should be generated. If everyone has the same expectations about when an email is sent, that is IMO a good thing. If users are allowed to not send emails or receive emails under certain conditions, then it can lead to situations where the author of a comment or change might have expected JIRA to notify someone and not follow up via email, where the recipient actually never received it in the first place. In my opinion, it's better to send the email and let the recipient decide whether to ignore it or not. I said the same thing over at the linked issue, although I can certainly see value in suppressing emails on minor edits and for certain users to prefer not to receive emails. Tough to satisfy everyone, I guess. Maybe the solution is to go forward with the ability for users to customize their email preferences as long as the JIRA administrator has given them that permission.
JP,
I would be very interested to hear your thoughts on Neal's and my feedback. When you have time, please let us know what you think. Cheers, Hi Anton & Neal,
Here is a few scenarios: First Well .. now I read that JRA-5959 and that would be the solution for this Fistr one. We have quite tight security settings.. e.g. 4 security levels
Sometimes we have to send comments to many customers than assignee+reporter (let's call then CC-users), but we do not want to drop security level. E.g. following situation.
One resolution:
Could it be possible to add similar list like "Watchers", where manager user (how has rights to add people to this list) could add these CC-users. Then it would be possible to add this "Users in CC-list" to security level. Would this be something that you Neal you thought? Hopefully you got my idea? Second
A few usability problems (see Ten Usability Heuristics :http://www.useit.com/papers/heuristic/heuristic_list.html
One resolution:
Administrator could give this viewing/choosing right to user/group/role/... BR, Hi JP,
Thanks for the update. I am glad that JRA-5959 will address some of your requirements. I will leave this issue open to track the requirements of your second scenario. However, please note, that as I have mentioned earlier this approach does go somewhat against the JIRA's policy to notifications, where administrators control who is notified of what events. I do not think we get a feature such as this one requested very often, and therefore we will have to see how much interest it attracts. Cheers, |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
In JIRA the decision about who is going to be notified when a change is made is left for the administrators. This way it is possible to ensure that required users are notified at all times.
Allowing the users who are making the changes to make a decision about who is notified kind of goes against that approach. It might also make new JIRA users quite confused as to what they are meant to do with the notification fields on the e.g. Add Comment screen.
May I ask if adding the functionality of e-mailing an issue to a set of users (or external e-mail addresses) would help you? If so, please vote for JRA-5959, as we are much more likely to implement this in the future than this improvement.
Please let me know what you think.
Cheers,
Anton