List Assignable Users

jira.list_assignable_users
ActionBusiness appsconnection required

Calls the Jira Cloud REST API with the connection's email and API token.

List the users who may be assigned issues in a project or on one issue.

Connection

Required
Yes — the node will not save without one
Auth type
Username & password
Providers
Jira
Secret shape
{"email", "api_token"}
Config it needs
domain
Resolved by
config.connection_id, else node.connection_id

Configuration

5 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
project_key
Project key to list assignable users for.
stringNo———
issue_key
Issue key to list assignable users for, instead of a whole project.
stringNo———
query
Narrow the list to users matching this name or email.
stringNo———
start_at
Index of the first result to return, for paging through a long list.
numberNo0≥ 0—
max_results
Maximum results to return in one call.
numberNo50≥ 1—
  • At least one of project_key, issue_key must be set.

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "max_results": 50,
  "start_at": 0
}

Output

One shape.

result

FieldTypeExample
users[].accountId
The user's Atlassian accountId.
string—
users[].displayName
The user's display name.
string—
users[].emailAddress
The user's email, when their profile shares it.
string—
users[].active
False for a deactivated account.
boolean—
users[].accountType
'atlassian', 'app' or 'customer'.
string—
count
How many items this call returned.
number—
{
  "count": 0,
  "users": [
    {
      "accountId": "",
      "accountType": "",
      "active": false,
      "displayName": "",
      "emailAddress": ""
    }
  ]
}

See List Assignable Users run in a workflow.

In a technical demo we add the Jira connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.