What permission is required to @ mention users who are not members of a classic software project?

[Max McDaniel]

I have a request from a project team to be able to @ mention a user on a ticket who is not a member of the project. This is a classic software project, so it uses a permission schema that has "Browse Project" granted for the group containing users we'd like to be able to tag. 

Is there a different permission required for users to be tagged and view issues in a project they're not a member of?

I (admin) am able to @ people in this project's issues, however a non-admin project member cannot. Is there a separate permission required to be able to tag others I need to assign to this role?

[Max Foerster - K15t · Accepted solution]

Hey @Max McDaniel

I think the Browse Users global permission is necessary for that.

Best, Max

[Max McDaniel]

Thanks @Max Foerster - K15t - I'll look into that. If set that global permission, then individual projects can restrict access as needed, correct?

[Max Foerster - K15t]

Hey,

not that I know right now. There is no project permission directly bound to this, only the global permission influencing user picker and lookups in general. It could be a side effect. I'll think about it. :) 

[Max McDaniel]

Oops, I was confusing Browse Users with Browse Issues. 

Interestingly, I have Browse Users granted to the user group but they're still unable to mention users. Will do some more investigating. 

[Max Foerster - K15t]

Hey Max,

do they have access to the project/issues? I don't exactly know all the background mechanics here (mentioning across different users groups, "Browse projects" project permission on top of that), especially on cloud. But I'd be very interested in your findings! :)

[Max McDaniel]

Turns out that there was an issue with the group that users were being provisioned to being different than what we had planned and had provisioned for. 

Good news, the permissioning seems to be working as expected.