Permission Scheme based on calculated Customfield is no more operational

[Vincent Thoulé _Alkaes_]

For Atlassian Dev. Team

Since many years (Jira 3.6.x), I use User Custom Field in Project Permission Scheme, as it is allowed in https://confluence.atlassian.com/adminjiraserver073/managing-project-permissions-861253293.html 

In some case, these User Custom Fields may be based on developed fields that extends the class com.atlassian.jira.issue.customfields.impl.MultiUserCFType.

When trying to migrate such User Field one of my plugin to Jira 9.x, I discovered that now, for (Multi/Single) User CustomField, the identification of Users initially based on method  Collection<S> com.atlassian.jira.issue.customfields.impl.AbstractMultiCFType<S>.getValueFromIssue(CustomField, Issue)

, is no more used in the resolution of allowed users for Permission Scheme.

The resolution is done in com.atlassian.jira.permission.DefaultIssueUserSearchManager.findTopUsersWithPermissionInIssue(String, long, UserSearchIssueContext, ProjectPermissionKey, int, PermissionSchemeLogic) based on a DAO : com.atlassian.jira.permission.QueryDSLSchemePermissionsDAO.findTopUsersFromUserCF(String, long, long, ProjectPermissionKey, int).

It causes that only users stored in CUSTOMFIELDVALUE table are found.

Any User Field, where members are calculated or stored by another way (Additional Table, REST call, ...), are no more usable in Permission Scheme.

Thanks for providing a Workaround !

Vincent