Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-3791

notification scripting


    • 7
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Atlassian Update - 19 March 2015

      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.

      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.

            Unassigned Unassigned
            28a9e6a89167 joe dane
            86 Vote for this issue
            52 Start watching this issue