Uploaded image for project: 'Confluence Server and Data Center'
  1. Confluence Server and Data Center
  2. CONFSERVER-33633

Improving notifications in Confluence (and JIRA)



    • We collect Confluence 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 Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      I have a feature request for a new option in the notifications settings (for Jira and Confluence): Only notfiy the user of the first change and mute notifications until the user opened the page/issue. This will reduce too much notifications in a short time frame. This is better than a daily summary and the user is still immediately informed of a change.

      After a little bit of brainstorming with a colleague about this feature request we came up with an even better idea with a different approach: Some kind of delayed summary notification: The change that would normally trigger a notifcation could be delayed by a custom period of time in hours (1 to 24h). In that period of time all changes of one Confluence-page or Jira-issue will be summarized and sent to the user after the period ends. For this to work, every page or issue needs an internal value for the time remaining. Short delays wouldn’t hurt the response time of a developer. Making this an option in the notification settings panel gives the user full flexibility how (s)he wants to be informed about progress in the project.


        Issue Links



              Unassigned Unassigned
              58075f67-99cf-4c92-8fe0-1b8ec7373af5 Deleted Account (Inactive)
              2 Vote for this issue
              4 Start watching this issue