Search Assignable Users
jira_search_assignable_usersSearch Jira for assignable users by display name, username, or email substring to obtain user identifiers for assigning issues. Requires a project or issue key.
Instructions
Search Jira users assignable in a given project or issue.
Use this when you have a display name / partial name / email fragment
and need a concrete identifier (name / key for Server/DC,
accountId for Cloud) to feed into assignee, reporter, watcher, etc.
Returns the full result set so the caller can disambiguate when several
users match — get_user_profile only resolves one identifier and is
not designed for human-name search.
Exactly one of project_key or issue_key must be provided — the
underlying API (/user/assignable/search) requires a project or issue
context and works without the global "Browse Users" permission that bot
accounts in locked-down DC instances often lack.
Args: ctx: The FastMCP context. query: Display name / username / email substring. project_key: Project key (e.g. 'DT') to scope the search. issue_key: Issue key (e.g. 'DT-779') to scope the search. limit: Maximum number of users to return.
Returns: JSON string: {"success": true, "count": N, "users": [...]} on success, or an error object on failure.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of users to return (default 20). | |
| query | Yes | Free-form text to search Jira users by: display name, username, or email substring (e.g. 'Smith', 'jane.doe', 'doe@example.com'). Server-side match is case-insensitive and partial. | |
| issue_key | No | Issue key to scope the search to (e.g. 'DT-779'). Required if project_key is not given. | |
| project_key | No | Project key to scope the search to (e.g. 'DT'). Required if issue_key is not given. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |