• Type: Suggestion
• Resolution: Won't Do
• Fix Version/s: None
• Component/s: None
• Labels:

  • affects-cloud

[CONFSERVER-41512] Disable Notify Watchers on Subsequent Page Edits After Being Unchecked on Another Page

Collapse comment: Adam Barnes (Inactive) added a comment - 21/Dec/2017 5:05 AM

Adam Barnes (Inactive) added a comment - 21/Dec/2017 5:05 AM

Atlassian update

Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. Thanks again.
Regards,
Confluence Product Management

Expand comment: Adam Barnes (Inactive) added a comment - 21/Dec/2017 5:05 AM

Adam Barnes (Inactive) added a comment - 21/Dec/2017 5:05 AM Atlassian update Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. Thanks again. Regards, Confluence Product Management

Collapse comment: Wendy Fergusson added a comment - 21/Jul/2016 3:14 PM

Wendy Fergusson added a comment - 21/Jul/2016 3:14 PM

This would be reverting from Confluence 5.9 behaviour to 5.8 behaviour. Please don't force this behaviour on everyone, it's not what everyone wants.

I think it's clear by now that no single notification default strategy is going to work for everyone. It needs to be configurable, at the site and space levels, and maybe at the page level too.

We like notifications. We were happy with Confluence 5.7 behaviour (checkbox default always on), were appalled at 5.8 (checkbox remembered for any page), and slightly mollified by 5.9 (checkbox remembered for same page). I know other people feel differently and that's fine. It just means we need a way to accommodate the differences.

Expand comment: Wendy Fergusson added a comment - 21/Jul/2016 3:14 PM

Wendy Fergusson added a comment - 21/Jul/2016 3:14 PM This would be reverting from Confluence 5.9 behaviour to 5.8 behaviour. Please don't force this behaviour on everyone, it's not what everyone wants. I think it's clear by now that no single notification default strategy is going to work for everyone. It needs to be configurable, at the site and space levels, and maybe at the page level too. We like notifications. We were happy with Confluence 5.7 behaviour (checkbox default always on), were appalled at 5.8 (checkbox remembered for any page), and slightly mollified by 5.9 (checkbox remembered for same page). I know other people feel differently and that's fine. It just means we need a way to accommodate the differences.