It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage
  • Community
  • Products
  • Jira
  • Questions
  • Please vote: Incredible confluence bug in the use of mentions @user !!! (no notification when added on page/comment edit!)

Please vote: Incredible confluence bug in the use of mentions @user !!! (no notification when added on page/comment edit!)

Sven Aug 09, 2012

Hello everybody,

please vote for this bug (perhaps you did not realize it - but it can hurt you! ;-)

https://jira.atlassian.com/browse/CONF-25518

EDIT/

The above bug has been fixed in 4.3! Thanks atlassian - well done.

Unfortunately now there is the following bug left:

https://jira.atlassian.com/browse/CONF-26289

=> This is annoying too, as every NEW mention should create an email-notification.

Without this, you can't organize/plan/etc. things in simple confluence tables. It will happen often that more than one mention will happen in an "organisational page".

Hope this will be fixed soon, too!

EDIT/

Sorry being "hard", but this is a showstopper!

In short: If you add a @username - mention somewhere in a page or in a comment, confluence will NOT send a notification e-mail to the user if it was added during a PAGE EDIT.

(notification is only send during a page or comment CREATION)

In 4.3 atlassian is even more pushing the @User mention functionality, so more Users will rely on it.

But this behaviour is absolutely UNEXPECTED!

We had already big trouble in our company, because the boss was sure that the collegue would be IMMEDIATELY notified and it was not the case!!!

Thanks for fixing this ASAP!

Make your great software even fantastic!

It should not be complicated to fix this. Without it we can't use the mention functionality, because users will forget about this big limitation and we will got even more problems ;-(

4 answers

2 votes

This CONF-25518 seems to have been fixed in Confluence 4.3 (tested on Confluence 4.3-RC1). There is another similar bug, that might sound the same, but is different which still affects Confluence 4.3-RC1 and is tracked separately at CONF-26289.

Sven Aug 09, 2012

Thanks. Thats good news. As you stated, this is only "half" the solution. But it's already promising. Hope the other bug will be fixed soon, too!

Voted up to raise the popularity of the bug

Just want to inform, it seems that we are working on it. Hopefully we would be able to fix it as soon as possible.

Cheers,
Septa Cahyadiputra

0 votes
Miyon Im Sep 09, 2013

I just voted this up as well. It's just awful the way it is now.

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published in Next-gen

Introducing subtasks for breaking down work in next-gen projects

Teams break work down in order to help simplify complex tasks. This is often done iteratively, with tasks being broken down into smaller tasks and so on until the work is accurately captured in well-...

940 views 12 15
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you