-
Bug
-
Resolution: Not a bug
-
Low
-
None
-
Minor
Issue Summary
It is common for users to enter the middle part of a name and expect user pickers to return results. This is the case when matching on email addresses, but not display names.
Steps to Reproduce
- Create an app that calls the /rest/api/3/groupuserpicker endpoint.
- Ensure a user exists with:
- Display name: "Foo Bar"
- email address: fbar@example.com
- Have the app call the endpoint with ?query=fo and observe the results.
- Have the app call the endpoint with ?query=ex and observe the results.
- Have the app call the endpoint with ?query=oo and observe the results.
Expected Results
At steps 3, 4, and 5, the user is returned in the results.
Actual Results
At steps 3 and 4, the user is returned in the results, but at step 5, not the user is not returned in the results.
Workaround
None
Context
[AI-1109] User picker APIs not returning matches for middle part of display name
Component/s | Original: XP - Content Search [ 60997 ] | |
Component/s | New: Search - Quick Search [ 75293 ] | |
Key |
Original:
|
New:
|
Project | Original: Jira Platform Cloud [ 18514 ] | New: Atlassian Intelligence [ 23110 ] |
Resolution | New: Not a bug [ 12 ] | |
Status | Original: Needs Triage [ 10030 ] | New: Closed [ 6 ] |
Component/s | New: TWP - Search [ 60997 ] | |
Component/s | Original: Integration - Identity [ 46556 ] |
Assignee | New: Sree Hari [ shari3 ] |
Component/s | New: Integration - Identity [ 46556 ] | |
Component/s | Original: Ecosystem [ 53294 ] |
Description |
Original:
h3. Issue Summary
It is common for users to enter the middle part of a name and expect user pickers to return results. This is the case when matching on email addresses, but not display names. h3. Steps to Reproduce # Create an app that calls the [/rest/api/3/groupuserpicker|https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-group-and-user-picker/#api-rest-api-3-groupuserpicker-get] endpoint. # Ensure a user exists with: ## Display name: "Foo Bar" ## email address: fbar@example.com # Have the app call the endpoint with ?query=fo and observe the results. # Have the app call the endpoint with ?query=ex and observe the results. # Have the app call the endpoint with ?query=oo and observe the results. h3. Expected Results At steps 3, 4, and 5, the user is returned in the results. h3. Actual Results At steps 3 and 4, the user is returned in the results, but at step 5, not the user is not returned in the results. h3. Workaround None |
New:
h3. Issue Summary
It is common for users to enter the middle part of a name and expect user pickers to return results. This is the case when matching on email addresses, but not display names. h3. Steps to Reproduce # Create an app that calls the [/rest/api/3/groupuserpicker|https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-group-and-user-picker/#api-rest-api-3-groupuserpicker-get] endpoint. # Ensure a user exists with: ## Display name: "Foo Bar" ## email address: fbar@example.com # Have the app call the endpoint with ?query=fo and observe the results. # Have the app call the endpoint with ?query=ex and observe the results. # Have the app call the endpoint with ?query=oo and observe the results. h3. Expected Results At steps 3, 4, and 5, the user is returned in the results. h3. Actual Results At steps 3 and 4, the user is returned in the results, but at step 5, not the user is not returned in the results. h3. Workaround None h3. Context See https://community.developer.atlassian.com/t/how-to-query-users-by-a-string-matching-middle-part-of-the-displayname/44973. |