Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Why am I suddenly unable to watch or unwatch Community posts?


I'm intensively using the 'watch' feature to keep track of Community posts I have contributed to or that are relevant to my areas of interest. Usually I watch multiple posts per day, and rarely remove a watch later on, so this is an ever growing and basically non maintained list of watches (~160 pages under 'Manage Settings -> Notifications' right now).

I've only just now noticed that the feature seems broken for me since about April 10th, which denotes the last day I have been able to apply a watch that actually sticks - the behavior since is not only dysfunctional, but also misleading as follows:

  1. I can seemingly 'watch' a post just fine, and the JavaScript changes the button to 'Watching', but after a page reload the watch is gone.
  2. The same goes the other way round, i.e. I can seemingly 'unwatch' a post, and the JavaScript changes the button back to 'Watch', but after a page reload the watch is still in place.
  3. I've checked my inbox and indeed all replies I've received since about April 10th seem to stem from posts that I watched before that date, i.e. the watches are seemingly simply not applied anymore (rather than this just being a display regression)

I've tested this with various browsers across systems to no avail, i.e. this is consistent for me, whereas a coworker can watch/unwatch just fine still.

Any help would be highly appreciated, insofar this regression significantly undermines my ability to follow up on the assistance I'm trying to provide to other community members.

Many thanks,

PS: I hope it goes without saying that no matter the root cause, communicating a supposedly successful outcome for any kind user interaction without a proper confirmation from the upstream service makes for an extremely bad user experience :/

4 answers

2 votes
Monique vdB Community Manager May 07, 2019

Thank you for flagging this, @Steffen Opel _Utoolity_I'm escalating this with the dev team and will keep you posted. 

1 vote
Dominic Lagger Community Leader May 06, 2019

Hi @Steffen Opel _Utoolity_ 

First of all, I did not realize, whether you mean on your confluence instance or you mean in the atlassian community. After clicking "Watch" on your topic and reload the page, I see the problem also. The "Watch" button is there again. 

I did not recognize that. Since the April 10th, I watched a lot, but never get emails... At this point, it's only becoming clear to me why. 

The strange thing is, I get notifications per mail when I comment to a post, that is for sure. So the "autowatch" function is still good. 

Could it be connected to the fact that in April the activity feed was broken? This blog post is from April 11th. 

I'm also interessted to a solution in this.

Thanks for bringing this to my attention.

Thanks for the confirmation, good to know (well, sort of) I'm not the only affected community member - I've also adjusted the question title and intro sentence to avoid the ambiguity.

Like Monique vdB likes this
0 votes
Dominic Lagger Community Leader May 20, 2019

Hi all,

I checked this today and it works again! 

Thanks for fixing! 

0 votes
Monique vdB Community Manager May 10, 2019

Update for those watching this thread: the dev team has a fix for this and it will be rolled out on Wednesday. Keep an eye out for the community release notes when we deploy the fix. Thank you for reporting!

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events