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.
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?
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
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.
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.
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.
@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.
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!
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.
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?
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?
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...
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.
@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
@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.
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