Our Connect App uses “GET /rest/api/2/user/search” to show a list of Jira human users. Before GDPR changes, our code used Email field data to get which user is an internal Jira technical account (they end with “@connect.atlassian.com”). Now, since Email addresses got hidden we need another logic to filter out technical users.
I can see in the documentation that the method “GET /rest/api/2/user/picker" has “excludeConnectUsers" boolean param which could be also useful in “/rest/api/2/user/search".
Is it possible to add “excludeConnectUsers" param to “GET /rest/api/2/user/search” method?
Also, we would gladly switch to use “GET /rest/api/2/user/picker" method instead of “GET /rest/api/2/user/search” but it seems that “GET /rest/api/2/user/picker" requires project info to be placed in the “query” param (if the “query” param is empty it returns “No project or issue key was provided”).