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

Watch notification emails the wrong page

Lis Riba January 8, 2012

We're running Confluence 3.5.13.

Autowatch is enabled, and we have installed the Descendent Notification Plugin.

Bob is watching a page titled Alpha, which has a child page named Foo.

There also exist pages Bar and Qux, which are in a different space from Alpha and Foo.

Bob is not watching any pages in that space.

Alice is editing page Foo, a child of Alpha. Carol is editing page Bar.

Alice saved changes to Foo at the same time that Carol saved changes to Bar.

Confluence sends Bob a notification.

The subject references page Foo, but everything in the email body is about page Bar.

Alice is still editing Foo, and a few minutes later, saves again.

Dave saves changes to page Qux at the same time.

Confluence sends Bob a notification.

The subject references page Foo, but everything in the email body is about page Qux.

This has happened on more than one occasion, to different recipients about different pages in different spaces.

I finally was able to determine this much (that both pages were being saved at the same time) when it happened to Bob twice in short succession.

Has anybody else seen or heard about anything like this?

Any idea what may be causing this or how to get it to stop?

3 answers

0 votes
Anna Gunich June 11, 2012

Please check this post

https://answers.atlassian.com/questions/14918/notifications-for-not-watched-space

Looks as if it is the same issue.

0 votes
Lis Riba January 10, 2012

Just found links where Adaptivist thinks the issue may be connected to the Descendent Notification Plugin:

Unfortunately, fixing it seems to be a rather low priority for them.

0 votes
Bob Swift OSS (Bob Swift Atlassian Apps)
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 9, 2012
Lis Riba January 10, 2012

Two possible additional datapoints:

1) As with the linked JIRA issue, it only started when we updated to 3.5

2) At least one user reported they stopped getting "rogue" notifications since they turned off autowatch. May not be related, but it's worth noting.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events