When will we be able to add a group in the manage watchers list for Confluence pages

A standard use case is for a team to want to be notified on changes to a page.

Adding or removing members form the group makes more sense than adding and removing individuals from the watch list for all pages owned by the team.

2 answers

1 vote

I don't think you will see this.  The point of watching is to enable an individual to say "I want to be kept updated", not to enable it to spam some group who probably have members that really do not care.

Why not let the administrator, the customer who pays for licenses and support decide whether adding a group makes sense. Your approach just makes it harder to spam. As it is I must add all 30 people on the team as watchers. It is an unnecessary administrative overhead.

I am not talking about users adding groups, but only admins just like only admins can add users as watchers now.

I'm sorry, I was not very clear in my answer. My point is that watching is designed for the individuals - it lets a person choose what they want to watch. Most places that let people add watchers quickly find that the value disappears. I want to watch what I choose to watch. I don't want emails just because someone else thinks I ought to watch it. There's a strong argument for removing ANY ability to add watchers other than by (explicit, clear and simple) rules or being the person clicking "watch". Groups would make over-enthusiastic (And hence counterproductive) drive-by watching even worse and even more likely to be simply filtered and ignored by users.

You were perfectly clear, but I could not disagree more.  Back to the original comment, its our workflow, its a feature we want.  Confused on why this decision would ever be made for a customer.

I suspect Atlassian have looked at how people use Confluence and taken on board the common complaint that their products often send far too much email, and have simply decided to not implement something that will spam people even more.

@Nic Brough [Adaptavist]

Your statement is fine for your use and philosophy but the customer buys products for functionality they need and want. If the end customers wants a functionality, then the vendor should strongly consider adding it or the customer might find another product that does provide the functionality. 

My point is that watching is designed for the individuals - it lets a person choose what they want to watch. Most places that let people add watchers quickly find that the value disappears. I want to watch what I choose to watch. I don't want emails just because someone else thinks I ought to watch it. There's a strong argument for removing ANY ability to add watchers other than by (explicit, clear and simple) rules or being the person clicking "watch". Groups would make over-enthusiastic (And hence counterproductive) drive-by watching even worse and even more likely to be simply filtered and ignored by users.

I completely agree.  Atlassian have considered it, and found it to be a bad idea for most of the users, so they've not done it. 

I should credit part of my reasoning to one of their product managers who was the one who pointed out that drive-by watching is a dreadful thing to inflict on users and simply makes the function useless because it trains them to ignore it.

The drive by watching still happens with people adding other users as watchers too liberally. And in that sense group watchers in Confluence is a bad idea. But it's hard to solve people problems with tools. The people find ways to misuse functionality.

It is for the good use cases that group watchers would be desired. 

Nic Brough [Adaptavist] Community Champion Friday

There are use cases for group watches, but there are stronger use-cases for not implementing it.  Atlassian have gone with the use-case of "don't allow people to bombard others with unwanted watches", as far more people want that, even many who think they want group watching. 

We like flexibility. We were fine with it as is until the VP of a major department wanted to use it. That's a good enough use case. 

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Posted Jul 10, 2018 in Confluence

We want to see the templates you've created in Confluence!

Hi Community, Jessica here from the Confluence Product Marketing team!  July’s community challenge is all about sharing pictures  — and as an extension of our first post on what ...

982 views 23 13
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you