Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-25750

Make the notify watchers functionality of page edits more discreet

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

      We find that a lot of users forget to or don't realise they should un-tick the "Notify watchers" check-box when making minor changes.

      One reason is possibly due to the location of the check box, it's not next to the save button as the preview button is between them.

      I suggest we simply have two buttons, [Save] and [Save and Notify]. The distinction is now clear, provides the same level of functionality and no backend changes need to be made, just the UI template.

            [CONFSERVER-25750] Make the notify watchers functionality of page edits more discreet

            Thanks @Simon Tost, seems I haven't seen that. I am testing it right now.

            From my point of view there are several use cases to deal with:

            1. Normal change - click save -> do not notify watchers at all
            2. Normal change - click save & notify -> do notify watchers within the next minutes (depending on the settings in Scheduled Jobs / Send Batched Notifications)
            3. Change that specifically mentions a user - click save -> do not notify mentioned user and other watchers at all
            4. Change that specifically mentions a user - click save & notify -> notify mentioned users immediately and other watchers within the next minutes (depending on the Send Batched Notifications settings)

            I am not quite sure yet, but I think that a mentioned user does not receive the notification emails immediately.

            Markus Raab added a comment - Thanks @Simon Tost, seems I haven't seen that. I am testing it right now. From my point of view there are several use cases to deal with: Normal change - click save -> do not notify watchers at all Normal change - click save & notify -> do notify watchers within the next minutes (depending on the settings in Scheduled Jobs / Send Batched Notifications) Change that specifically mentions a user - click save -> do not notify mentioned user and other watchers at all Change that specifically mentions a user - click save & notify -> notify mentioned users immediately and other watchers within the next minutes (depending on the Send Batched Notifications settings) I am not quite sure yet, but I think that a mentioned user does not receive the notification emails immediately.

            @Markus Raab: As mentioned before: There is also the addon No email storm which has a bit more configurability

            Simon Tost [TNG] added a comment - @Markus Raab: As mentioned before: There is also the addon No email storm which has a bit more configurability

            Markus Raab added a comment - That could help: https://marketplace.atlassian.com/plugins/com.tngtech.confluence.plugins.two-save-buttons/server/reviews

            Totally agree with the previous posters! Two buttons as suggested inclusive shortcut would be very handy.

            Markus Raab added a comment - Totally agree with the previous posters! Two buttons as suggested inclusive shortcut would be very handy.

            Simon Tost [TNG] added a comment - - edited

            @John Donohoe: There is a plugin for that: https://marketplace.atlassian.com/1211747

            EDIT: No email strom plugin

            Simon Tost [TNG] added a comment - - edited @John Donohoe: There is a plugin for that: https://marketplace.atlassian.com/1211747 EDIT: No email strom plugin

            The implementation for the linked item: https://jira.atlassian.com/browse/CONF-8276 is not a good as the one suggested here - which I was also going to suggest.

            The comments on https://jira.atlassian.com/browse/CONF-8276 make clear why.

            Could this suggested implementation be re-evaluated please?

            John Donohoe added a comment - The implementation for the linked item:  https://jira.atlassian.com/browse/CONF-8276  is not a good as the one suggested here - which I was also going to suggest. The comments on https://jira.atlassian.com/browse/CONF-8276  make clear why. Could this suggested implementation be re-evaluated please?

            Covered off by linked issue

            Sherif Mansour added a comment - Covered off by linked issue

            Brett Ryan added a comment -

            Hi John, this is correct. Many users know they should un-tick the check-box but forget; it's two clicks required, one to un-tick, another to save.

            My suggestion would simply bring the function into a single click, which is more obvious to a user and easier to understand.

            The welcomed side-affect to this approach in my mock-up is to move Save away from Cancel, I don't know how many times I myself have accidentally clicked Cancel instead (RSI makes using a mouse error-prone).

            Brett Ryan added a comment - Hi John, this is correct. Many users know they should un-tick the check-box but forget; it's two clicks required, one to un-tick, another to save. My suggestion would simply bring the function into a single click, which is more obvious to a user and easier to understand. The welcomed side-affect to this approach in my mock-up is to move Save away from Cancel , I don't know how many times I myself have accidentally clicked Cancel instead (RSI makes using a mouse error-prone).

            Hi Brett,

            Thanks for taking the time to raise a request!

            So are you getting complaints from users about too many edit (or other?) notifications at the moment?

            John

            John Masson added a comment - Hi Brett, Thanks for taking the time to raise a request! So are you getting complaints from users about too many edit (or other?) notifications at the moment? John

              Unassigned Unassigned
              6c4fdac73624 Brett Ryan
              Votes:
              8 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: