ADO.NET Provider for Jira

Build 26.0.9770

AssignableUsers

Returns users assignable to issues in a specific Jira project.

View-Specific Information

SELECT

The provider applies filters server-side only when supported for the specific column and operator, as documented in the Columns section. All other filters are processed client-side.

You must specify a ProjectKey or ProjectId to retrieve results. If neither is specified, the provider automatically queries the Projects table to retrieve the required identifiers. This may result in increased query times.

Jira Cloud

On Jira Cloud, the following columns support server-side filtering with the = operator:

  • ProjectId: Filters by project ID. When provided together with ProjectKey, ProjectId takes precedence and the ProjectKey filter is ignored.
  • ProjectKey: Filters by project key. Ignored when ProjectId is also specified.
  • AccountId: Filters by the user's Atlassian account ID.
  • DisplayName: Filters by the user's display name.
  • EmailAddress: Filters by the user's email address.
  • AccountType: Filters by the user's account type.

For example, the following queries are processed server-side:

SELECT * FROM AssignableUsers WHERE ProjectKey = 'TEST';
SELECT * FROM AssignableUsers WHERE ProjectId = 10000;
SELECT * FROM AssignableUsers WHERE ProjectKey = 'TEST' AND AccountId = '712020:fcd95543-59da-42bc-a0f2-4ab4265f07d4';
SELECT * FROM AssignableUsers WHERE ProjectKey = 'TEST' AND DisplayName = 'John Doe';
SELECT * FROM AssignableUsers WHERE ProjectKey = 'TEST' AND AccountType = 'atlassian';

When neither ProjectKey nor ProjectId is specified, the provider automatically queries all projects and retrieves assignable users for each:

SELECT * FROM AssignableUsers WHERE DisplayName = 'John Doe';

Jira Data Center

On Jira Data Center, the following columns support server-side filtering with the = operator:

  • ProjectKey: Filters by project key.
  • Name: Filters by the user's username. Using this column performs a single-user lookup by exact username.
  • DisplayName: Filters by the user's display name (passed as the username query parameter to the Jira API).

For example, the following queries are processed server-side:

SELECT * FROM AssignableUsers WHERE ProjectKey = 'TEST';
SELECT * FROM AssignableUsers WHERE ProjectKey = 'TEST' AND Name = 'jdoe';
SELECT * FROM AssignableUsers WHERE ProjectKey = 'TEST' AND DisplayName = 'John Doe';

When ProjectKey is not specified, the provider automatically queries all projects and retrieves assignable users for each:

SELECT * FROM AssignableUsers WHERE Name = 'jdoe';

NOTE: Starting with Jira Data Center version 8.20, the startAt offset parameter is no longer supported on the user/assignable/search endpoint. As a result, the provider fetches up to the maximum of 100 users per project. On earlier Data Center versions (prior to 8.20), standard pagination is fully supported.

Columns

Name Type References SupportedOperators Platform Description
AccountId [KEY] String Users.AccountId = Cloud The accountId of the user, which uniquely identifies the user across all Atlassian products.
Key [KEY] String Users.Key Server The key of the user.
ProjectId [KEY] Integer Projects.Id = Common The ID of the project to search for assignable users.
ProjectKey [KEY] String Projects.Key = Common The key of the project to search for assignable users.
Name String = Server The name of the user.
DisplayName String = Common The display name of the user.
EmailAddress String = Common The email address of the user.
Active Bool Common Indicates whether the user is active.
TimeZone String Common The time zone specified in the user's profile.
Locale String Common The locale of the user.
AccountType String = Cloud The account type of the user.

Copyright (c) 2026 CData Software, Inc. - All rights reserved.
Build 26.0.9770