In the attached screenshot you can see my name has been @mentioned by the user, but this notification email is not as a result of the mention. In this case (and inconsistently) I have not been sent any notification email with 'mentioned you' in the subject, which I rely on for filtering in gmail.
Is there some hidden logic for when this email notification is or isn't sent?
Has anything been done about this issue? It's really causing me problems as I can't reliably keep track of when someone asks me a specific question by mentioning me. I can't filter by my name as Gmail's filters seem to apply that to every Jira email. I'm guessing this is because my name is also in my email!
The only workaround I could come up with is to disable autowatch and be much more restrictive about what tickets I listen for. This isn't really a good solution though IMO. Plus, there's no way to unwatch in bulk so unless I find a hack to unwatch I'm still going to get spammed for the foreseeable future until these tickets become inactive.
We have the same issue.
Not sure if you may be running into this as well, but I realized that when you mention someone in a comment, they are only emailed if they are mentioned in the very first comment in an instance. Say I highlight text, comment on it and mention @JamesBond. James will get an email notification. But, if I reply to that comment and mention @Dr.Evil, he will not receive an email.
This is silly, any one who is mentioned should be notified!
Ran in to this issue took me hours to solve it and I am a pretty experienced SysAdmin with almost 20 years of experience. Turns out it points back to my directory server. How, you ask? We use AD, and it turns out that you MUST have an email address populated in the user's 'email' attribute fielding AD. Under user properties, General tab, email field. If you are using Jira's internal directory, the email address is a required field for every user so that should work every time. If you are using AD, talk to your SysAdmin, unless you are your own SysAdmin in which case do it yourself, and have him/her update the 'email' field for all users that need this feature enabled. I would suggest telling them to do it site wide. This resolved my issues with email notifications on mentions. First, send a test email from jira. Make sure the user you use to send email from Jira has the right password and all your email settings are correct. If you can send test emails from Jira and users are receiving them, then your email stuff is squared away and you likely don't have email addresses defined on your directory. Try that, it fixed my issues.
+1 to fix this.
This has been causing our team a lot of grief for some time. Essentially there is a culture of saying @mentions don't work in JIRA, and people miss key updates.
For me I had, constantly have to remove myself as a watch from tickets, so that I have some chance of seeing @mentions.
Absolutely need the text "mentioned you" in the subject line of the email, which does not appear to be the case, if you are a watcher, or assignee. Those are the tickets that I would care about most.
I would suggest the email was sent because your are a watcher of the issue where the comment was done. Check the Notifications Sections of that project and the Roles to see if you are in any group or Role that would be notified on comments done to an issue.
You are added to the watchers list every time you comment on an issue so generally after commenting on an issue you'll be kept updated of the comments and other activities according to the Notifications Scheme.
If you are on OnDemand and would like more personalized help about it, feel free to open a support request at support.atlassian.com
The @mention email contains information specific to the fact that your name was mentioned. The regular watcher email does not contain this info. Thus it is incorrect to claim "the email was sent because your are a watcher". An email which calls out your @mention is not sent. If the watcher notification was modified to include this information, then you would be correct. But currently it is not. This is a poor experience.
The alternative would be to add @mention info into the regular watcher notification emails. This would satisfy the need for @mention info while avoiding duplication. Personally, I'd be happy for either one. The current situation is the worst of all worlds where I get the @mention emails for a project until someone adds me as a watcher and suddenly I stop getting them. Thus any email filtering/highlighting I do is rendered useless.
It is a really bad behaviour, that @mention does not get priority over the other notifications. This is an real issue as I can't modify the notification rules (as we do not get admin access for Jira in our company - only central admin can do). Now my users are either get overloaded with notification mails (as I can't filter them properly in my mail program) or loose the @mention mails, if there on any other list, because they are watcher, reporter or assignee. I can't believe that this has not been fixed over such a long time!!
We just transitioned from Outlook to gmail which seems incapable of filtering on exactly "[~firstname.lastname]", instead finding "firstname lastname" in every single email, so that solution is out the window.
Atlassian, why is it that 5 years later we're still talking about this bug? Do you guys ever fix major usability issues?
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
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!
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