Interface UserPickerSearchService
- All Known Implementing Classes:
DefaultUserPickerSearchService
ApplicationUser objects based on a partial query string-
Method Summary
Modifier and TypeMethodDescriptionbooleancanPerformAjaxSearch(JiraServiceContext jiraServiceContext) Deprecated.Returns true only if UserPicker Ajax search is enabled AND the user in the context has com.atlassian.jira.user.ApplicationUser Browse permission.booleanDeprecated.Determines whether the given user could perform AJAX search.booleancanShowEmailAddresses(JiraServiceContext jiraServiceContext) Deprecated.Whether or not the UserPicker Ajax should search or show email addressesfindUsers(JiraServiceContext jiraServiceContext, String query) Deprecated.Get Users based on a query string.findUsers(JiraServiceContext jiraServiceContext, String query, UserSearchParams userSearchParams) Deprecated.Get Users based on a query string.findUsers(String query, UserSearchParams userSearchParams) Deprecated.Get Users based on a query string.findUsers(String nameQuery, String emailQuery, UserSearchParams userSearchParams) Deprecated.Get Users based on query strings.findUsersAllowEmptyQuery(JiraServiceContext jiraServiceContext, String query) Deprecated.Get Users based on a query string.getUserByName(JiraServiceContext jiraServiceContext, String query) Deprecated.Returns a user by exact usernamebooleanuserMatches(ApplicationUser user, UserSearchParams userSearchParams) Deprecated.Determine whether a user matches the search criteria specified in theuserSearchParamsparameter.
-
Method Details
-
findUsers
Deprecated.Get Users based on a query string.Matches on start of username, full name and email as well as all the tokenised (on spaces, '.', '@' etc) words Only returns active users.
Results are sorted according to the
UserCachingComparator.- Parameters:
jiraServiceContext- Jira Service Contextquery- String to search for.- Returns:
- List of
ApplicationUserobjects that match criteria. - See Also:
-
getUserByName
Deprecated.Returns a user by exact username- Parameters:
jiraServiceContext- Jira Service Contextquery- String to search for.- Returns:
- The
ApplicationUserobject with supplied username.
-
findUsersAllowEmptyQuery
Deprecated.Get Users based on a query string.Matches on start of username, full name and email as well as all the tokenised (on spaces, '.', '@' etc) words This will search even if the query passed is null or empty. Only returns active users.
Results are sorted according to the
UserCachingComparator.- Parameters:
jiraServiceContext- Jira Service Contextquery- String to search for.- Returns:
- List of
ApplicationUserobjects that match criteria. - See Also:
-
findUsers
List<ApplicationUser> findUsers(JiraServiceContext jiraServiceContext, String query, UserSearchParams userSearchParams) Deprecated.Get Users based on a query string.Matches on start of username, full name and email as well as all the tokenised (on spaces, '.', '@' etc) words
Results are sorted according to the
UserCachingComparator.If the users in the database change during this call results might not be consistent if a post processing filter and a result limit is used.
- Parameters:
jiraServiceContext- Jira Service Contextquery- String to search for.userSearchParams- Additional search parameters- Returns:
- List of
ApplicationUserobjects that match criteria. - Since:
- 5.1.5
-
findUsers
Deprecated.Get Users based on a query string.Matches on start of username, full name and email as well as all the tokenised (on spaces, '.', '@' etc) words
Matches email only when userSearchParams.canMatchEmail() is true.
Results are sorted according to the userSearchParams.comparator. If userSearchParams.comparator is null, no sorting will be performed.
If the users in the database change during this call results might not be consistent if a post processing filter and a result limit is used.
- Parameters:
query- the query to search username, display name and email addressuserSearchParams- the search criteria- Returns:
- the list of matched users
- Since:
- 6.2
-
findUsers
List<ApplicationUser> findUsers(String nameQuery, String emailQuery, UserSearchParams userSearchParams) Deprecated.Get Users based on query strings.Matches nameQuery on start of username, full name and email as well as all the tokenised (on spaces, '.', '@' etc) words
Matches emailQuery on start of email, as well as the tokenised words. Email matching is performed only when userSearchParams.canMatchEmail() is true.
Results are sorted according to the userSearchParams.comparator. If userSearchParams.comparator is null, no sorting will be performed.
If the users in the database change during this call results might not be consistent if a post processing filter and a result limit is used.
- Parameters:
nameQuery- the query to search username and display name.emailQuery- the query to search email address, subject to userSearchParams.canMatchEmail.userSearchParams- the search criteria- Returns:
- the list of matched users
- Since:
- 6.2
-
userMatches
Deprecated.Determine whether a user matches the search criteria specified in theuserSearchParamsparameter.allowEmptyQuery in
userSearchParamsis ignored.- Parameters:
user- the user to be matcheduserSearchParams- the search criteria- Returns:
- true if the user matches the search criteria
- Since:
- v6.2
-
canPerformAjaxSearch
Deprecated.Returns true only if UserPicker Ajax search is enabled AND the user in the context has com.atlassian.jira.user.ApplicationUser Browse permission.- Parameters:
jiraServiceContext- Jira Service Context- Returns:
- True if enabled, otherwise false
-
canPerformAjaxSearch
Deprecated.Determines whether the given user could perform AJAX search.- Since:
- v6.2
-
canShowEmailAddresses
Deprecated.Whether or not the UserPicker Ajax should search or show email addresses- Parameters:
jiraServiceContext- Jira Service Context- Returns:
- True if email addresses can be shown, otherwise false
-
UserSearchServiceinstead. Since v7.0.