Jira Cloud "api/3/user/search" does not differentiate app users

Hello!
It appears the latest update to Jira Cloud has changed how rest/api/3/user/search REST API method works.

Currently, it returns both Jira users and app users under “atlassian” accountType value.
As a result, it is impossible to distinguish actual users from the system app users in JSON response.

It is a glitch or is there any other way how to “get rid” of system add-on users?

Returned JSON:
{
“accountId”: “111111111111111111111”,
“accountType”: “atlassian”,
“active”: true,
“avatarUrls”: { … },
“displayName”: “Slack”,
“emailAddress”: “”,
“locale”: “en_US”,
“self”: “https://xxxxxxxxxx.atlassian.net/rest/api/3/user?accountId=111111111111111111111”,
“timeZone”: “Europe/London”
},
{
“accountId”: “222222222222222222222”,
“accountType”: “atlassian”,
“active”: true,
“avatarUrls”: { … },
“displayName”: “John Smith”,
“emailAddress”: “”,
“locale”: “en_US”,
“self”: “https://xxxxxxxxxx.atlassian.net/rest/api/3/user?accountId=222222222222222222222”,
“timeZone”: “Europe/London”
}

Apps used to have “app” as accountType value in the past.

Hi Yevgen,

A similar request is already submitted (REST API returns "accountType"="atlassian" for app/addon users ) and a corresponding Jira issue is tracked under the following link: https://ecosystem.atlassian.net/browse/ACJIRA-1903

This appears to be a bug in Jira Cloud api.