|
Notifications in general do not respect permissions. This bug is being tracked in
At the moment, I think the only workaround within JIRA is to write one's own workflow post-function on the 'create issue' transition. For instance, Vincent Massol did this here: http://blogs.codehaus.org/people/vmassol/archives/000842_writing_a_jira_3_plugin.html A small but critical change to generic notifications system would be the ability to filter that only issues which are greater or equal in severity are send. Of course it is easy to see, that other operators like equal, not equal and lesser than can be added as well. This would help especially in cases where only critical issues should generate email to a specific address for futher processing, but of course an interim solution is to make custom notification java class.
Another vote - same reasons as Mika - in particular we'd like high importance issues to trigger external alerts. Currently we would have to filter externally.
This has been request by my customers as well - esp. component-based notification. (JA-282)
The ability to tailor notifications so that folks see just what they need to see, no more and no less, is critical. Right now, I am fighting a constant feast or famine battle with the "JIRA Flood" (or jiralood if you want JIRAlang) with our team.
If we dial things up, folks start getting flooded with emails. If we dial it back, issues start getting missed. This issue has been around for over 4 years. The last Atlassian comment on it was over three years ago. What does it take for this one to get attention? The recent functionality in 3.13 was a breath of fresh air. Really delivering critical functionality. But there are more issues which need to be addressed. Please look for them and get them on the road map. It would be great if you started laying out roadmaps for the next 24 months or so (with the further out they get, the more fuzzy they get). |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
I tried to create a similar workaround by:
(1) Creating JIRA users just for group notifications (and use a distribution list as their e-mail address), such as billing-notifications, operations-notifications, etc for different departments.
(2) I added each of those users to just one Issue Security Level (such as "billing", "operations", etc).
(3) But when users enter new issues and assign that issue to one of the security levels above, the notification goes out to all my custom users even though only one has Issue Security Level permission to view the issue.
Hope that makes sense, but it was an ugly hack that still didn't work - your recommendation would be outstanding! I see a lot of other open notification issues that have not been responded to, so evidently, notifications aren't very high on the priority list yet.