Can't @Mention other users?

[Scott Beeson]

I have a fairly new set up.  I am the admin.  I have about 5 other users currently.  For some reason I cannot "@" mention anyone but myself.  Is there a setting somewhere?

[Scott Beeson · Accepted solution]

Apparently they have to be part of the jira-users group, even though I created a custom group and gave it all the JIRA access I wanted.

[Nic Brough -Adaptavist-]

That doesn't sound right. I can mention people outside JIRA users in the jira I've got here.

[Scott Beeson]

I agree it's weird, but I triple checked the behavior. I couldn't tag someone, added them to jira-users, could tag them. Did the same for the next user and so on. /shrug

[Scott Beeson]

I just quadruple checked it. I typed @a and saw two names. I removed one of them from jira-users and reloaded the page. When I typed @a I only saw the other user.

[Nic Brough -Adaptavist-]

Ah, hang on. You can only @mention people who have the right to view an issue. So I suspect that you've got jira-users in a role that allows browse, which means removing them from there removes their access, and hence, you can no longer mention them.... So expected symptoms, but a slightly different route than you thought.

[Scott Beeson]

The first one I tried to mention a user on was an issue she created and commented on, so that shouldn't be the problem...

[Nic Brough -Adaptavist-]

Creating or commenting on an issue does not give you the right to see it. If you remove her from jira-users, she can't see it any more, so you can't mention her until you put her back in.

[Scott Beeson]

How can she comment on an issue she cannot see?

[Nic Brough -Adaptavist-]

Because when she made the comment, she was in jira-users, so she could see it.

[Scott Beeson]

She was never in jira-users until I started troubleshooting why I couldn't mention her. She was not in jira-users when she created the ticket or when she commented.

[Nic Brough -Adaptavist-]

So she was in another group that gave her access when she created and commented.

[Scott Beeson]

Yes, the custom group I mentioned.

[Nic Brough -Adaptavist-]

Yup, there you go - she can be mentioned when she can see the issue, and can't be mentioned when she can't see it. That's what the docs say.

[Scott Beeson]

... She was in "Company Employees" group, which I created to give everyone access. She was NOT in jira-users. She created a ticket. She commented on the ticket. I could NOT @mention her. I added her to jira-users and then I COULD @mention her.

[Steven Breton van Groll]

You have to look into the global permissions. Just add a group (i.e. jira-users) to the permission "Browse Users". Then every users in this group can mention other users in comments.

[Sait Erbil]

I can mention as an admin however I gave browse user permission to all of my user groups but some groups still can't mention somebody. Its weird that, in one of these groups, some members can mention somebody, others cannot.

[Eduardo Ramos]

I'm having the same problem here. I've set up a group who have the Browse Users setup correctly. They are part of the scheme with the same level access to others who can use @mention, but they cannot do it. The only difference is that this is a vendor, so I created a separate group for them.  What am I missing?

[Narasimha murthy]

Hi Nic,

my issue is little different. i am the admin for jira and i can "@" mention users also, but in the dropdown when we do this "@" i dont see all the existing users. i can see only other jira admins/ jira-administrators group members.

what might be the issue?

FYI- we are seeing this after we enabled the LDAP yesterdaty

[Nic Brough -Adaptavist-]

You are probably being limited by the same as above - the missing people are not in groups that allow access to the issues.

[Narasimha murthy]

i can see them only when they are member of that project but its not happening in our cloud instance which is using SAML. i can mention any name in the comment even if they are not part of that project unlike our on prem instance 

[Nic Brough -Adaptavist-]

On Cloud they probably are part of the project, they only need read-access, which is the default.

There's no point mentioning people who don't have any access to something - they won't get told they have been named, and it doesn't give any other functions.

[Narasimha murthy]

understood the point here! but in the cloud instance all users are showing up if i want to comment on any issue and in any project.  Is that cuz of permission differences.?

[William Pettersson]

This worked for us:  You have to look into the global permissions. Just add a group (i.e. jira-users) to the permission "Browse Users". Then every users in this group can mention other users in comments.

[Narasimha murthy]

Thanks william,

yes, that works.

[Loco After]

Thanks for the info @Steven Breton van Groll!!!

[Peter Van Geenhoven]

To be honest I really disapprove of this Global Permissions way of working for mentions... I have several user groups (one for each 3rd party we are dealing with) and several boards (also mostly 1 per 3rd party). I want my third party users that create defects be able to mention me or one of my colleagues. I don't want them to be able to browse all users and user groups because quite frankly they have no business seeing who else we do business with.

Atlassian should implement a finer grained security here: you should be able to browse people in your own usergroup for example...that way I can add our core responders in each of the 3rd party groups and they can mention us, without having access to all our user groups and users... Again, this can be sensitive from a security point of view: some of our 3rd parties are direct competitors of one another and they would not be happy that the other one can see who is working for them on a project with us.

[Thomas Gottmann]

@Peter Van Geenhoven this is exactly the case and we did not activate the proposed solution for our customers.

[Peter Van Geenhoven]

Same here! Seems like an easy "next best thing" or quickfix for Atlassian to allow Mentions of users in the same usergroup without requiring Global Permission.

[Anne-Marie Scheidegger]

@Peter Van Geenhoven Thank you for your comments. I have been waiting for this fix for a couple of years now (see my comment from 2017? above) and could never believe that we are the only ones with this problem...

[Ermal Bizhuta]

+

[Math]

+1

[Peter Van Geenhoven]

@Anne-Marie ScheideggerSeems like there are not many people who are terribly concerned with their security....which I find rather careless in this day and age...

[Sean Thompson]

Right on @Peter Van Geenhoven - I'm a client in a very similar situation and it drives me crazy I can't at mention my PM, for example, to get her attention on an issue. Now I understand why I don't have that permission and I won't be asking for it.

[Davy Claes]

Why can't Atlassian limit the Jira 'user mention' functionality to the issue permission "Assignable User" (from the JIRA project permission scheme) instead of limiting this to a Global Permission? That way a JIRA user can mention any users whom the JIRA user can assign the ticket to.

[Mark Hawkins]

@Peter Van Geenhoven Your comment is the exact same situation as ours and what is logged here: https://jira.atlassian.com/browse/JRASERVER-7467?focusedCommentId=2274733&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-2274733.

We need to UPVOTE this issue on the link above, so that Atlassian sit up and take notice and implement the easy fix. Well it seems easy enough.

cc @Sean Thompson @Davy Claes @Math @Thomas Gottmann @Anne-Marie Scheidegger @Ermal Bizhuta @Nic Brough -Adaptavist- 

[Anne-Marie Scheidegger]

@Mark Hawkins Thank you for sending us the link on where to vote (which I have passed on to my team, too) and sorry I never took the time to file or find a corresponding JIRA bug :flushed

[Peter Van Geenhoven]

I added my votes, but the deafening silence of Atlassian on this one doesn't promise much good. Seems they are more interested in changing the UX every single week than addressing some basic security issues.

[felix.weber]

just to update on this..seems its getting fixed:

https://confluence.atlassian.com/adminjiracloud/permissions-for-classic-projects-1001823931.html
=> The issue is caused by an intentional design in Jira’s backed that couples the Browse Project and View issue permissions. We’re currently working to decouple these permissions.

For cloud there is also an Article which might help you to find the root cause:

https://confluence.atlassian.com/jirakb/mentions-and-autocomplete-are-not-working-in-jira-cloud-779160727.html

[Danno]

I realize I am late to the game on this post but I had an issue where one of my users couldn't @mention anybody. It turns out he had been removed from the default Jira-users-group and the group he was in didn't have the global Browse permission. I had tried adding him as a single user to the project permissions to no avail and the permission helper wasn't helpful in this case since there isn't an @mention permission to give.

Anyway, I think everybody here had figured out what to do in their own instances. In my case, I have a fellow admin who is there in case I leave and that tests my admin skills on a regular basis.

[Berry van Es]

I had the same problem and fixed it as followed;

You need to add Brose permissions to the group.

Go to: System > Global permissions > Click on dropdown 'Permission' and select 'Browse Users' > Now select the group you want to give this permission in the dropdown next to group > Click on Add.

This should give everybody in that group the ability to use @Mentions

I hope this helps!

[Tyler Trollinger]

This is the best answer!

[noah.duncan@gmail.com]

Fixed my issue, thanks!

[HN]

If you want to do this at a project level, goto your Project Administration Page > Permissions > Browse Projects (add role/group/user etc.)

[Natalia Muntyan]

awesome! Have been struggling for quite a while! Helped!

[Marcus Morczinietz]

Thanks so much!

[Yan Wu]

Thanks a lot, it works!

[Shailesh Gambhir]

Perfect answer, Solved the Issue thanks :)

[Milos Tomic]

Thanks @HN!

[Luis Camacho]

Thanks! Straight forward! It solved my issue.

[miriam-hopton]

This helped SO much! THANK YOU THANK YOU!! Simple and easy fix. ;)

[Volker Hirschberger]

Worked, Thanks!

[Steffen Sønderby]

Just what I needed, thanks! But when I tag someone, they don't receive any notification. Is there a setting for this as well?

[Natalia Giuliani]

Thanks for this... I always forget this when creating a new group!

[Thivaher]

Bless you Berry. It was driving me crazy

[Volodymyr Mysnyk]

Thanks a lot!

[Steve Gullon]

This was a God send, thanks!

[Thomas Gottmann]

If the customer gets this permission, can he also see different projects that are usually not possible for him? 

[Fokke Lingeman]

This solved it for me, thanks! (y)

[BobFix]

This should be the accepted answer and first listing on the page.  Thank you for the information!

[lucianovici]

JIRA 7.3.3 Administration Gear > System > Global Permissions > Add permission:

- Browse users

- The group

[miriam-hopton]

Awesome- thank you for this!! This fixed my problem. :D

[lucianovici]

You're welcome! :)

[Harish Tuccapuram]

Thank you this fixed my problem.

[Natalia Lezhai]

What if the group does not appear in the search section?

[Deleted user]

Even people who don't have permissions to view project can be mentioned via "[~email]". 

[Scott Beeson]

Good to know!

[Julia Pinto]

On my Jira it actually has to be [~username], which some times is the email, sometimes it is just the part of it before the "@" or the name.

[Andrew Peret]

Removing the user from the user group and readding the user to the user group worked for us for one user that was not able to mention.

[Mark Hawkins]

@Andrew Peret that only a suitable option, if all your users are part of the same organisation, and you don't mind your users seeing everyone within your organisation when they try @ mention someone. The issue most people are explaining here, is that they have contractors; agencies; clients; and people not part of their organisation, and for obvious reasons you do not want them to SEE all other users in the platform, when they @ mention a user in a comment or ticket.

Currently JIRA doesn't allow you to restrict @ mention permissions in this way, it's simply either ON or OFF which doesn't work for most people. More explained here in this comment: https://community.atlassian.com/t5/Jira-questions/Can-t-Mention-other-users/qaq-p/5238#M436446

[Andrew Peret]

@Mark Hawkins , understood.

Our setup does restrict users more granularly.  Mention permissions is not system wide, but at a group level.

I went through the forums and suggestions on how to resolve our issue, but nothing worked.  

Only one of our users was not able to mention and he had the same permissions as other users that were able to mention.

To resolve, I removed the "broken" user from all groups and re-added that user to the same groups.

It is probably a bug and uncommon edge case.

[Faisal Shamim]

How can I highlight user "@" in comment box of any project, I have put jira-user group under Browse Users but its not working , Notification is going but user is not highlight in comments. can anyone please help

Thanks

[Dimitri Vedeneev]

So I've found this page: https://confluence.atlassian.com/jirakb/mentions-and-autocomplete-are-not-working-in-jira-cloud-779160727.html

In it it describes to Add that permission (Browse Users is not a default permission that exists in a default confluence install on the cloud). Scroll to the bottom of the global permissions page, and Add the permission and group. Should work after that.

[Chad Augustine]

I have Jira 4.1 and double checked my permissions, but when I type in the "@" symbol, I don't get an option to add anyones name. 

All I get is an "@" symbol.

Does anyone know when feature was added?  

[ScottC]

Added in 5.0

https://confluence.atlassian.com/jira/jira-5-0-release-notes-269980782.html

[John Cobbs]

Removing groups and site access from the user, then re-adding seems to fix the issue.

[Nick Carn]

I had same problem - could not mention or add watchers.  Our admin added me to jira-developers and it fixed the problem.

[Natalia Lezhai]

What if the users don't auto populate at all? 

[Andy - PTC Redundant]

Then there is most likely an issue in the settings of the Jira-Users-group.

[Anand_Sasi]

If there are any complete idiots(other than me) looking for how to add an issue link in comments:

Entering issue number in square brackets [ABCD-100] work if the wiki rendering is turned on for that project. But Jira converts it to a link only after you save the comment, not before. Until then you just see it as plain text.

I wasted  two hours checking field configurations and project settings without ever saving the comment. Jira convert the User mention(@username) to link without posting the comment and I assumed the Issue link would also work the same way.

[Andy - PTC Redundant]

That's handy to know!

Are you on Server, Data Centre or Cloud?

[Anand_Sasi]

Cloud

[Andy - PTC Redundant]

Also good to know! Thanks for sharing @Anand_Sasi - have great day!

[Danno]

I realize this is an old post but I'll add to it anyway.

So in the cloud just type the issue key and then a space and it will convert to the link immediately.

[Andy - PTC Redundant]

THIS IS WHY I LOVE COMMUNITY.... 💝

As Jira Admin I always forget these little details (embarrassing... I know!) but have no fear! Community is hear! YEAH :)

And a 4 year old question too. BRILLIANT! 👍🥇

[Mark Brennan]

This is great info thanks!

Now, if I want a customer to have access only to one project, not the others, I assign them to a project role, and associate that project role to a permission scheme, allowing that person to have Browse Projects only for that project. But now I need to enable them to @mention people. Any ideas?

[Nic Brough -Adaptavist-]

Make sure they have browse users permission.

This has nothing to do with what project they are using or have access to .

[Anne-Marie Scheidegger]

I have the same question: It seems that the browse users permission is global, but I would like a customer with access to only one project to only see the people that have access to that project (ie the development team and the users at that customer) but not other customer users that have permission to other customer projects. The goal is to protect the customers privacy and not expose their contacts to other customers of ours. Is there a way to do that?

[Ellen Beentjes]

I have the same issue, they should be able to tag e.g. a specific group, but don't see other external users.

[Aaron Jones]

@Anne-Marie Scheidegger We are encountering the same issue where we would like to mention others when having only a guest account.  Any chance you created/found a work around over the past year?

[Anne-Marie Scheidegger]

Hi Aaron, no we haven't found a solution, but I have also not looked into it again. Either we look at the issues every day to see what the latest changes are, or we add at least someone from the team to the watcher list, so we get notified of changes... But I still wish the @mention-list would work per defined group...