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

quiet period for update notifications


    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • Scheduled Tasks
    • None
    • 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.

      In the notifications scheme, how about an option to wait 2 or 3 minutes before sending out a notification, in case there are any updates to follow?

      Almost all of our bugs involve someone creating the issue, and then attaching a screenshot, and often updating part of the bug they missed (like component or assignee), resulting in 2-3 emails per issue.

      Optionally, the problem could be alleviated by making "screenshot added" a distinct event from issue updated. Or making a "quiet save" option and leave the control in the users hands.

      Email overload is my biggest complaint of jira right now.

            Unassigned Unassigned
            0e1541592a16 kris helenek
            0 Vote for this issue
            0 Start watching this issue