Related issue I just opened: https://jira.atlassian.com/browse/CONFSERVER-53343

That could help: https://marketplace.atlassian.com/plugins/com.tngtech.confluence.plugins.two-save-buttons/server/reviews

We added support for this in Cloud via our add-on at https://marketplace.atlassian.com/plugins/bandage-conf/cloud/overview It requires that your users install a browser extension, but it has drastically helped companies where this was beta tested.

In the mean time: There's a plugin for that: https://marketplace.atlassian.com/1211747

EDIT: No email strom plugin

@Atlassian: This issue is back again for us (notify by default always on) since activating syncrony on confluence 6.0.3 and 6.0.7. Looks like we have a regression on our hands, which could be handled by reopening this ticket.

Can others confirm this?

The solution suggested under https://jira.atlassian.com/browse/CONF-25750 would have been much better than this and would address the criticisms above. Can this be reopened for consideration?

I would still prefer having a global admin or, even better, per page option of checkbox behavior. I would like to see the choice of three: "default on", "default off" or "remember last setting".

Some pages in my space are much more important than others and I would rather have more notifications than running a chance of missing an important notification. Some of the pages are less important so it's fine if the user forgets setting the checkbox. The way it behaves now, I'm having to constantly remind people to be conscious of the checkbox. You wouldn't believe how many people even fail to notice the checkbox and having unchecked it once for whatever reason, remain totally oblivious of it until told explicitly.

@Robin Peters: Per @sherif Mansour / Atlassian comment above, each page now remembers your last "notify watchers' state. Try this:

1. Create two new pages.
2. Update one of the pages, deselecting the 'Notify Watchers' checkbox.
3. Edit the same page again and observe the 'Notify Watchers' checkbox is deselected by default.
4. Edit the other page. Observe the 'Notify Watchers' checkbox is selected by default.@

I downloaded V5.8.2 and could not find the settings to deactivate the notify watchers checkbox by default.
And the jQuery Script of your knowledge base won't work either.

While I agree this is better than defaulting the notify watchers checkbox to enabled every time, it's still not a very nice implementation from a use case standpoint. A user will still have to remember to check/uncheck the box to provide or not provide notifications to the users, so accidental notification is still going to occur. On top of that, the user is going to have to remember to recheck the box prior to saving when they want to notify users, so notifications will also be missed. And overall this is a page-by-page change to the functionality, forcing the user to put additional thought into the saving of every page they edit.

It sounds very trivial, but it is a very difficult behavior to get correct every time you save a page. It was mentioned that the two button solution did not fair well in UX. I propose that you have a user randomly make format changes to a few pages during a busy workday which have a dozen watchers. Allow them to do so for a week and see who still doesn't understand and embrace the two button solution over the checkbox.

Hi Everyone,
Thank you for your patience and feedback with this feature suggestion.

We're pleased to announce in the next upcoming release of Confluence we will be resolving this issue. We've tried to avoid adding more settings to the product (we've already got plenty!) and our solution for this, which we are confident reaches the same outcome is that we will now remember your last preference for "Notify watchers". So once you've un-checked it, will remember that until preference on any page until you change it back (and visa versa).

For Cloud customers, this will be available the next Confluence release. For Server customers we hope to deliver this to you in our next major version (Confluence 5.8) within the next couple of months.

We are still determined to tackle the overarching problem around reducing the amount of email you receive in Confluence. This is in our long-term roadmap (we're exploring things like digest emails etc...) and will be continuing to make an effort to improve this in the future.

We're grateful for such an engaged customer community, your awesome ideas and feedback.
Cheers from the Confluence Team!