GET /rest/api/2/user/assignable/search

Returns a list of users that can be assigned to an issue. Use this operation to find the list of users who can be assigned to:

a new issue, by providing the projectKeyOrId.
an updated issue, by providing the issueKey or issueId.
to an issue during a transition (workflow action), by providing the issueKey or issueId and the transition id in actionDescriptorId. You can obtain the IDs of an issue's valid transitions using the transitions option in the expand parameter of Get issue.

In all these cases, you can pass an account ID to determine if a user can be assigned to an issue. The user is returned in the response if they can be assigned to the issue or issue transition.

This operation takes the users in the range defined by startAt and maxResults, up to the thousandth user, and then returns only the users from that range that can be assigned the issue. This means the operation usually returns fewer users than specified in maxResults. To get all the users who can be assigned the issue, use Get all users and filter the records in your code.

Privacy controls are applied to the response based on the users' preferences. This could mean, for example, that the user's email address is hidden. See the Profile visibility overview for more details.

Permissions required: Browse users and groups global permission or Assign issues project permission

Servers

https://your-domain.atlassian.net

Query parameters

Name	Type	Required	Description
`startAt`	Integer	No	The index of the first item to return in a page of results (page offset). Default value: 0
`query`	String	No	A query string that is matched against user attributes, such as `displayName`, and `emailAddress`, to find relevant users. The string can match the prefix of the attribute's value. For example, query=john matches a user with a `displayName` of John Smith and a user with an `emailAddress` of johnson@example.com. Required, unless `username` or `accountId` is specified.
`username`	String	No	This parameter is no longer available. See the deprecation notice for details.
`maxResults`	Integer	No	The maximum number of items to return. This operation may return less than the maximum number of items even if more are available. The operation fetches users up to the maximum and then, from the fetched users, returns only the users that can be assigned to the issue. Default value: 50
`accountId`	String	No	A query string that is matched exactly against user `accountId`. Required, unless `query` is specified.
`recommend`	Boolean	No	Default value: false
`actionDescriptorId`	Integer	No	The ID of the transition.
`sessionId`	String	No	The sessionId of this request. SessionId is the same until the assignee is set.
`project`	String	No	The project ID or project key (case sensitive). Required, unless `issueKey` or `issueId` is specified.
`issueKey`	String	No	The key of the issue. Required, unless `issueId` or `project` is specified.
`issueId`	String	No	The ID of the issue. Required, unless `issueKey` or `project` is specified.

How to start integrating

Add HTTP Task to your workflow definition.
Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
Click Test request to test run your request to the API and see the API's response.