Prevent access to custom field values shared between projects

[Anateus]

I have several custom fields that are used for two projects. Text fields, selects, user pickers.

Each project has its own values that should be inaccessible to the other one. I.e. if we add a user to the user picker in PRO-1, it should not be offered as suggestion in PRO-2, nor be accessible to users from PRO-2 using JQL search.

Will this be doable with separate contexts for each project, or do we need completely different custom fields?

For reference, an identical problem is described here - in case I did not describe it properly:
https://community.atlassian.com/t5/Jira-questions/Prevent-Search-Lookup-for-assignees-from-returning-all-assigness/qaq-p/630864

[Nic Brough -Adaptavist-]

Yes, you can use different contexts, but you won't be able to stop the search from making suggestions.  Searches do not run in a project context, so Jira has no way to know which context you might want to be using.

[Anateus]

Hi Nic, just to be extra sure I edited my post with an identical issue (in case mine isn't described well enough).

So there is absolutely no way to prevent search suggestions with values/users added from other projects? Nothing in permissions that could affect it? 

[Nic Brough -Adaptavist-]

No, as I said, the searches don't have a context to work with.  They have no choice but to offer all options.

[Ravi Sagar _Sparxsys_]

Hi @Anateus 

Yes you can create different context for those list type fields. That is what contexts are for.

Ravi

[Anateus]

Hi Ravi, I edited my post with an identical issue - in case mine isn't described well enough. According to Nic above, it's not possible to prevent them from seeing other values/users.