Any progress?

Currently users from one client can see e-mail adresses from other clients which has to be restricted.

This is very much needed, I still don't understand if Atlassian understands the importance of issues raised ...also when you merged Opsgenie with JSM, Teams is not working without Browse User permission. There should not be any restriction to add users to Browse User permission to get some function to work. If we need any users to view all users, we can add to that permission but not for all users. 

Please get this feature asap.

Hey!

I top this comment:

"This is also an issue for us because we have a lot of users in our Jira user directory that do not have JIRA access. It should never be possible to assign issues to them."

This is exactly what I am facing right now. I would like to limit user picker dropdown list for Assignee/Reporter and other user picker lists to specific group or project. 

This would be a great initiative. 

We have a field that is type "user picker / multiple users". It allows you to select Portal Only Customers. This should not be allowed as they are not users of Jira.

Hence, I vote for this change 

Thank you for the Update from October 2023 but that Article is Cloud related.
We're on Server/DataCenter and need a solution for Datacenter.

When I check the (global) Browse Users description it says

Ability to select a user or group from a popup window as well as the ability to use the 'share' issues feature.

So IF I'd restrict the browse users function, then our technicians can NOT share the ticket with their colleagues. If I do no restriction the technicians can also mention and share to developers, which they should not.

We need the ability to restrict "Browse Users" not only for groups but also for purpose.
I as Agent do require the ability to mention and share to everyone.
Reporter, however, should only share and mention between Reporters, maybe Agents, too, but Certainly no Developers
Developers also should be able to share and mention other Developers, but they also should not have contact to the Reporter directly.

BR
Christian

PS: @Atlassian: please do not forget DataCenter. We pay a FORTUNE for your licenses and it s***s that only Cloud is developed further. I understand your strategy to push cloud, but then LOWER the License Cost for DataCenter!!
PPS: I know the request is only 10 years old and Atlassian only considers tickets which are at least 15 years old. But maybe you can make an exception?

This is crucial for security purposes. Please provide us with a resolution.

The watchers of this ticket may be interested in this post: Improvements to Browser User permissions (User Searchability by Project). Please add any questions or comments there.

Any updates on this please?

Does anyone know if this relatively new announcement will help correct this annoyance or is it unrelated?
https://community.atlassian.com/t5/Jira-Service-Management-articles/A-dedicated-product-access-role-for-internal-customers-in-Jira/ba-p/2279244#M2631

Absolutely need this to support some of our workflows. We plan on implementing a single customer-facing project since it needs to interface with other internal Jira Product Discovery and Software projects. Having customers appear in our user pickers is not okay.