-
Suggestion
-
Resolution: Won't Fix
-
None
-
7
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Hi everyone,
In an effort to consolidate issues that accurately track our development priorities, I am going to close this issue. We do hope to address JIRA's notification system with more customizable notifications, but the improvements we are seeking to make are more accurately described in JRA-2565. We have no plans to introduce additional scripting capabilities.
As always, please don't hesitate to contact me if you have any questions.
Thanks
Dave Meyer
Product Manager, JIRA Platform
the notification scheme stuff is very cool, but could be better.
on several occasions now, I've wanted something where a notification would be sent in certain situations, but I'm unable to express the situations using a scheme. in particular, although I can trigger a notification on issue create, I can't say "trigger on issue create, if the issue is in component X, and was not created by user Y".
it's hard to see a simple way of enabling this from the GUI.
here's one possibility. allow the list of notification triggers to be edited. instead of having a single "issue created" trigger, with some number of notifications attached to it, allow any number of "issue created" triggers. each trigger could have an optional attribute, which is a boolean valued expression in some simple language. the notifications for the trigger would fire if the expression evaluated to true in the context of the issue in question.
so, for example, you could have some number of primitive operators:
component C <-- true if the current issue is in component C
reporter R <-- etc.
beforetime T <-- true if the issue was created before time T
and some boolean connectives, and you're done. when an issue is created, JIRA looks for all "issue created" triggers, executes their condition expressions in the context of the current issue, and fires the notifications if the condition is true. or better, the "issue created" trigger type could just be incorportated into the expression.
there are probably other places in JIRA that could use this sort of thing. listeners, for example, could be configured to fire only for a certain project.
- incorporates
-
JRASERVER-2579 Notification based on permission
- Closed
- is duplicated by
-
JRASERVER-6467 Update notification scheme to allow emails to be sent off of issue priority or add ability for notification scheme turn on/off configuration via a permission that can be granted to a project administrators
- Closed
-
JRASERVER-15273 Add ability to specify a group as a "Lead" for a component
- Closed
- is incorporated by
-
JRASERVER-2565 Rule-based Notification Schemes
- Gathering Interest
- is related to
-
JRASERVER-2644 Notifications Customisable by End Users
- Closed
-
JRASERVER-5509 Reporter Group permission
- Gathering Interest
- relates to
-
JRACLOUD-3791 notification scripting
- Closed
-
JRASERVER-5227 Rule-based / pluggable permission types
- Closed
-
JRASERVER-10521 Different notification schemes for different components in a project
- Closed
-
JRASERVER-10685 Ablitiy to group the user by component
- Closed