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

Throw multiple events per transition

XMLWordPrintable

    • 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.

      Use Case: a need to notify two distinct user groups of some workflow transition. For a project there may be a constant number of users who need to be updated on an 'Issue Updated', but, perhaps there is an approvals step whereby a QA engineer approves the validity of some bug, and a development team is then notified (but not necessarily yet assigned).

      JIRA doesn't let you throw multiple events (2) per transition, yet, I can't think of a reason why it couldn't?

            [JRASERVER-19678] Throw multiple events per transition

            Peter White [Atlassian] added a comment -

            Thanks Neal.

            Peter White [Atlassian] added a comment - Thanks Neal.

            Neal Applebaum added a comment -

            I can't think of a reason why it couldn't

            See JRA-6344, JRA-16863, JRA-12362

            According to Anton:

            We cannot generate 2 events for a change as this will break a lot of existing IssueListeners. To implement a fix for JRA-12362 we would need to change how the Notification sub-system deals with generated events rather than generate multiple events. The notification sub-system would need to allow one to e-mail a certain set of users whenever a particular field is changed, no matter what operation has been performed.

            An operation should only trigger one event, as otherwise chaos will occur when it comes to consuming those events in listeners.

            Personally, I like chaos if it solves my problem

            Neal Applebaum added a comment - I can't think of a reason why it couldn't See JRA-6344 , JRA-16863 , JRA-12362 According to Anton: We cannot generate 2 events for a change as this will break a lot of existing IssueListeners. To implement a fix for JRA-12362 we would need to change how the Notification sub-system deals with generated events rather than generate multiple events. The notification sub-system would need to allow one to e-mail a certain set of users whenever a particular field is changed, no matter what operation has been performed. An operation should only trigger one event, as otherwise chaos will occur when it comes to consuming those events in listeners. Personally, I like chaos if it solves my problem

              Unassigned Unassigned
              pwhite Peter White [Atlassian]
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: