Problem

When searching for users in the Actor field within Jira Cloud Automation, the system uses the GET /rest/api/2/user endpoint, which returns both Atlassian accounts and customer accounts. However, the Automation UI filters out customer accounts from the dropdown, making it impossible to select a customer as an actor. This behavior is not visible to users unless they inspect the API response, leading to confusion—especially after migrations where legacy customer accounts may have similar display names as system users and they are shown up as a result in API response when inspected.

Suggested Solution

Update the Automation UI and/or backend logic to ensure consistency between the API response and the UI dropdown:

• Exclude customer accounts from the API response when searching for actors in the Automation UI.

Why This Is Important

• Users expect to see all accounts returned by the API in the UI dropdown. The current mismatch can lead to wasted troubleshooting time and support requests.
• After migrations, legacy customer accounts with similar names (e.g., "Automation for Jira") can appear in the API but not in the UI, causing further confusion and potential misconfiguration.

Workaround

(Add a workaround, if available)