Include Atlassian service accounts in the Automation "Assign work item" user picker (assignable users)

XMLWordPrintable

    • Jira Software, Jira Service Management, Jira Work Management

      Issue Summary

      The Automation "Assign work item" action (Specify user) excludes Atlassian service accounts from its user picker, even when those accounts can be assigned to work items manually. Service accounts that hold the Assignable User permission should be selectable as automation assignees.

      Environment

      • Product: [Jira / Jira Service Management]
      • Site setup:
        • Cloud instance using Atlassian service accounts as standing assignees
        • Service accounts granted the "Assignable User" permission via the project's permission scheme

      Current Behaviour and Use Case

      Teams use dedicated Atlassian service accounts as the standing assignee for work items routed by automation (e.g. security exceptions or vulnerability triage queues). These service accounts:

      • Are valid, active accounts on the site, and
      • Can be assigned to work items manually (they appear in the normal issue assignee picker and hold the Assignable User permission).

      However, when configuring an automation rule with the "Assign work item" action (or Edit work item -> Assignee) using the Specify user option, the picker excludes Atlassian service accounts.

       

      Cause: the picker calls JiraUserClient.findAssignableUsers, which defaults userAccountTypes to ['atlassian','customer']. Because service accounts are not of type atlassian or customer, they are filtered out of the results.

      As a result, a service account that is fully assignable manually cannot be selected as the target user in the automation assignee picker, so teams cannot build a straightforward "auto-assign to service account" rule through the UI.

      Requested Feature

      Align the Automation assignee resolution with manual assignment by including Atlassian service accounts that hold the Assignable User permission for the target project, rather than filtering them out.

      Workaround

      Currently, the only available workaround is to use smart values:

      1. Bypass the picker by setting the assignee via the account ID in an advanced / JSON field edit, e.g.:
        { "fields": { "assignee": { "accountId": "SERVICE_ACCOUNT_ACCOUNT_ID" } } }

              Assignee:
              Unassigned
              Reporter:
              David Chan
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: