We are using JIRA cloud. Out of the blue, without any permission changes, some of my resources were unable to be @tagged on JIRA ticket comments. I have checked the "Browse users and groups" - and i have given that permission to everyone. All these resources have been added to the projects under "people".
This was working until yesterday, and now it isn't. No changes were made.
Any help will help.
Check once whether they have the browse project permission.
https://confluence.atlassian.com/adminjiracloud/managing-project-permissions-776636362.html
if the users dont have the browse project permission, one can't tag them in comment.
Thanks Sandesh.
I had specified it like this which was not working:
Project role:
Users
Assignee
Administrators
Reporter/Creator
zSuper User
Developers
But then, when i add the Group: 'acces-jira' it worked. But that poses another issue. I had set it up such that only people in the specific projects could view the projects. But by adding the group, now all the resources can see all the projects.
But when I mention project roles this was working until yesterday.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If users have "browse users and groups" permission and if they are part of the roles you are mentioned - it should work. Ensure resources/users are part of the roles you mentioned.
If it was working yesterday, In any case project admin removed the users/resources from the roles??
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is my current permission setup:
Browse Projects: All project roles (Users, Assignee, Administrators, Reporter/Creator, zSuper Userz, Testing/Maintenance, Developers, Tempo Project Managers & External User)
Browse users and groups: access-jira
Issue still persists - still can't tag anyone in the comments section.
But only respective projects are shown based on the project roles - so that is working!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yeah, if resources are part of the roles you mentioned, then resource should be able to be tagged in comments.
If nothing works create a role/group and add all the resources who are unable to be tagged -> mention that role/group in browse project permission.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Strangely, without changing anything from specified earlier, it started working :)
Thanks for your help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.