+1 We want to watch labels

+1

Also needed here! Please give this feature a higher prio...

+1 Having to create multiple blogs for people to watch has been a nightmare. That's our workaround. When an announcement applies to multiple projects, some inevitably get multiple emails from every blog they're watching. We'd much prefer to have a Watch By Label. 

+1 and bump... please reconsider.  I see the sister ticket for the cloud service is still "gathering interest".

Thanks for your interest in this issue.

While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We appreciate the benefits of such requests, but don't plan to work on this for the foreseeable future.

This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status.

+1 for suggestion of @Thomas Krause. Great idea!!

in general: current watching with feed builder is nasty usability compared to all other performance tweaked features within Confluence! My problem to win users is this setup process which is even simpler in other applications.

Please compare: step 1 (use feed builder to set up label watch) + step 2 (bring that feed-link to mail like outlook) + step 3 (configure rule to move rss-items to inbox) VERSUS step 1 (press watch button) ==> Result: receive mail notification to inbox. BUT rss-feed doesn't contain color-highlighted diffs!

Additionally: pages are filtered and listed with labels - dynamic content is dependent from labels! It's just so obvious to link a communication channel directly to the content structured for the target audiences in Confluence. But this one

• must show the diffs and
• must be easily implemented (imagine a "cql watch macro" which I can put to my context. This one displays a watch button which users can hit.

Fine. Performant. Attractive. Highly customizable to any Confluence context.

So easy to set up for newbies: your new role is it-management? -> watch label it-management. DONE! The person is in the information flow of anything related to his organisational task. That eases a lot.

We want to watch just labels. We filter by labels and want to throttle too many watcher notifications. If users know which labels to follow it would greatly reduce spam notifications.

A more generalized approach would be to watch CQL (results). Whenever the result set changes (removed, changed, added) a notification would be triggered. This would cover a lot of use cases, like

• watch page trees,
• watch labels (and combinations)
• watch just the meeting-notes within a space
• watch blog posts of a given topic (aka label)

Furthermore it could supersede the good old feedbuilder (configurerssfeed.action) and cover its features completely.

Configurable notification channels would be

• email (also bulked)
• workbox
• RSS (pseudo notification for feed builder features)
• HipChat (extensible)
• other notification sinks (ie. MSTeams) - extensibe

+1 Us too. We have exactly the same model as Rick Beecroft above. People post blog posts about whatever the heck they feel like. They're encouraged to be noisy and not worry too much about the quality of relevance of the content. However, adding labels to publish to the relevant people, across departments, would allow interested parties from different departments to get involved. 

+ 1 We need this also