Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-7917

Roll up changes before emailing them out


    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

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

      Here's an issue we're running into. People will often make a lot of sequential changes to a bug, and depending on whether or not the workflow screens directly support doing all those changes at once, subscribers to change notifications may get blasted with emails that are all related to the same bug.

      Example: someone writes up a bug, goes back and edits a custom field that wasn't on the bug creation screen, attaches a screen shot, then assigns it to someone. Anyone subscribed will get four emails for one bug being created.

      Suggestion: have Jira wait x minutes on the most recent change to an issue to let it "settle" before sending out a notification email, and have that email contain all the changes at once.

            Unassigned Unassigned
            46dd16050868 Scott Bilas
            55 Vote for this issue
            35 Start watching this issue