JIRA Zones plugin restrict user searching via JQL and @mentions?

[Jordan M_ Pflum]

JIRA Zones plugin refers one to Atlassian Answers for support.

https://marketplace.atlassian.com/plugins/at.celix.jira.plugins.zones

On the topic of multi-tenancy:

https://celixaddons.atlassian.net/wiki/display/ZON/Zones+for+Multitenancy

We are concerned about the ability to search for users from other organizations via JQL, like "Assignee = ", or "Reporter = ".  The system prompts suggestions from the whole user directory.  Will Zones by customer supersede this?

Also, when using @Mentions, will Zones restrict the suggestions prompted here similarly?

Also, if I am going down a dead-end by researching this plugin to solve these problems, does anyone have other suggestions?

Thank you!

[Jenny Bellas]

Thanks Jordan. We have thought of that option too, but you have to buy a separate license package for each environment, correct?

[Jordan M_ Pflum]

I think technically yes....... we are actually negotiating directly with Atlassian on that.

[Jenny Bellas]

We are looking at this plug-in so that we can have a custom User Picker field that works, with the Browse User permission turned OFF. We have not found a way to limit the visibility of showing all users with Browse User permission ON. Your post is quite old. Did you find any other solution?

[Jordan M_ Pflum]

Hey there, we unfortunately never did find a fix to this (our interest in this plugin dead-ended too). Turns out this problem is a big enough deal that my organization is going the route of separate JIRA environments for projects where the clients need access to limit exposure. Projects where clients do not need access can be hosted together, as internal employees don't have a problem searching for one another.