The pre-selected values for the smart user picker. Supports only Users and Teams default value hydration. If the DefaultValue contains only an id and type (it conforms to an OptionIdentifier) then the values will be automatically hydrated. If the value has a name then it is considered hydrated and will be ignored. Uses Confluence and Jira if called from there, else uses Identity or Legion for teams. If a value could not be found, or there was a network failure during the hydration, the value will be rendered with the label 'Unknown'. Else, if there were any other error during default value hydration, no default values will be rendered, use onValueError to handle this. defaultValue differs from value in that it sets the initial value then leaves the component 'uncontrolled' whereas setting the value prop delegates responsibility for maintaining the value to the caller (i.e. listen to onChange)

Identifier for informing the server on where the user picker has been mounted. Unlike User Picker, the fieldId in Smart User Picker is mandatory. The server uses the fieldId to determine which model to utilize when generating suggestions. All fieldId's will be bucketed into a model that provides generic smart results, except "assignee", "mentions" which are specifically trained for Jira Assignee and @Mentions. For specifically trained models, please contact #search-plex.

The base URL of the site eg: hello.atlassian.net

Hydrated user suggestions to show when the query is blank. If not provided, smart user picker will still provide a smart-ranked list of suggestions for blank queries. Please refer to @atlaskit/user-picker for OptionData type.

Context information for analytics. Eg: if a user picker was put inside a comment, the childObjectId would be the ID of the comment. Optional, but please provide if available.

• The container Id to identify context.
• e.g. Jira: projectId. Confluence: spaceId. Bitbucket: repositoryId.

Time to debounce the suggestions fetching (in milliseconds). Defaults to 150ms.

Function to transform options suggested by the server before showing to the user. Can be used to filter out suggestions. The results of filterOptions are the results displayed in the suggestions UI.

Whether to include groups in the resultset. Only supported for Confluence. @default false

Whether to include teams in the resultset. @default false

Whether to include users in the resultset. @default true

Whether to include non licensed users in the resultset. @default false

An identifier of the closest context object, e.g. issueId, pageId, pullRequestId. Used for analytics. Optional, but please include if available.

Custom handler to give opportunity for caller to return list of options when server returns empty list. this is called if server returns empty list. This will NOT be called if props.filterOptions returns empty list.

Error handler for when the server fails to suggest users and returns with an error response. error: the error. RecommendationRequest: the original recommendationRequest containing the query and other search parameters. This may be used to provide a fail over search direct to the product backend. Helper fail over clients exist under /helpers. Note that OnError results are filtered.

Error handler used to provide OptionData[] values when the server fails to hydrate the defaultValue prop's values.

Function to generate the byline of each option. The server response is provided as an argument to the function.

Prefetch the list of suggested assignees before the user picker is focused. WARNING: please consider carefully before deciding to prefetch your suggestions as this will increase the load on the recommendations services (has caused HOTs). Please give #search-plex a ballpark on the expected request volume.

Id of the user interacting with the component. If principalId is not provided, server will extract principalId from the context header, assuming that the user is logged in when making the request. @default “context”

Product-specific Attributes - you should pass in the attribute type that matches your current SupportedProduct. Currently we support additional attributes (BitbucketAttributes) for bitbucket and (ConfluenceAttributes) for Confluence.

Product identifier. If you are an NPF, please ensure your product has been onboarded with Cross-product user-search @see https://developer.atlassian.com/cloud/cross-product-user-search/ If you are still waiting for CPUS, you can use the people productKey in the interim.

Filter to be applied to the eventual query to CPUS for user suggestions. Example:account_status:"active" AND (NOT email_domain:"connect.atlassian.com") will remove inactive users from the list of suggestions.

Identifier for the product's tenant, also known as tenantId or cloudId

Identifier for the organization in which to search for teams.