-
Bug
-
Resolution: Tracked Elsewhere
-
Medium
-
None
-
5.0.0
-
None
-
4
-
1
-
Severity 2 - Major
-
2
-
Issue Summary
User picker in the "Request participants" field can't find the user by their email address (or any other attribute) when the user has a very short name, as described in https://jira.atlassian.com/browse/JRASERVER-69836 and https://jira.atlassian.com/browse/JRASERVER-65142
Expected Results
Find the user at least by their email address
Actual Results
The user can't be found due to less relevant users showing up in higher in the search results.
Workaround
Change user email to include a custom tag. E.G. User Ha Ha with email address ha.ha@example.com
is not searchable by their full email due to the fact that current Jira implementation of user search treats both the "." and "@" characters as search terms dividers, and search results are limited to 20 and ordered alphabetically. Changing the user email to "ha.ha+jira@example.com" will make them searchable through "ha+jira" term. The emails will arrive to their inbox tagged with "jira" label. The tag can be any word of your choosing, however, people sharing the request will have to know it to be able to search for the user.
For resolution of the issue, please refer to Jira tickets JRASERVER-69836 and JRASERVER-65142
- is caused by
-
-
- Gathering Impact
-
-
-
- Gathering Impact
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-12341] User picker for Request Participants cannot find a user with a very short name when there are other users that have their name somewhere as part of their name or username
| Assignee | New: Bartosz Ornatowski [ bornatowski ] |
| Resolution | New: Tracked Elsewhere [ 15 ] | |
| Status | Original: Needs Triage [ 10030 ] | New: Closed [ 6 ] |
| Link | New: This issue is caused by JRASERVER-65142 [ JRASERVER-65142 ] |
| Link | New: This issue is caused by JRASERVER-69836 [ JRASERVER-69836 ] |
| Description |
Original:
h3. Issue Summary
User picker in "Request participants" field cant find the user by their email address ({*}or any other attribute{*}) when the user has a very short name. Example: !image-2023-01-24-17-05-45-332.png! - Edit an issue and try to add the user as a Participant using its email address: !image-2023-01-24-17-18-32-827.png! - The user can't be found by email, full name or shortname h3. Steps to Reproduce Not possible to recreate h3. Expected Results Find the user at least by their email address h3. Actual Results The user can't be found by any means h3. Workaround No workaround available |
New:
h3. Issue Summary
User picker in the "Request participants" field can't find the user by their email address ({*}or any other attribute{*}) when the user has a very short name, as described in https://jira.atlassian.com/browse/JRASERVER-69836 and https://jira.atlassian.com/browse/JRASERVER-65142 h3. Expected Results Find the user at least by their email address h3. Actual Results The user can't be found due to less relevant users showing up in higher in the search results. h3. Workaround Change user email to include a custom tag. E.G. User Ha Ha with email address [ha.ha@example.com|mailto:ha.ha@example.com] is not searchable by their full email due to the fact that current Jira implementation of user search treats both the "." and "@" characters as search terms dividers, and search results are limited to 20 and ordered alphabetically. Changing the user email to "ha.ha+jira@example.com" will make them searchable through "ha+jira" term. The emails will arrive to their inbox tagged with "jira" label. The tag can be any word of your choosing, however, people sharing the request will have to know it to be able to search for the user. For resolution of the issue, please refer to Jira tickets JRASERVER-69836 and JRASERVER-65142 |
| Summary | Original: When adding a user as a Participant, user picker for Request Participants can find the user | New: User picker for Request Participants cannot find a user with a very short name when there are other users that have their name somewhere as part of their name or username |
| Description |
Original:
h3. Issue Summary
User picker in "Request participants" field cant find the user by it's email address ({*}or any other attribute{*}) when the user has a very short name. Example: !image-2023-01-24-17-05-45-332.png! - Edit an issue and try to add the user as a Participant using its email address: !image-2023-01-24-17-18-32-827.png! - The user cant be found by email, full name or shortname h3. Steps to Reproduce Not possible to recreate h3. Expected Results Find the user at least by it's email address h3. Actual Results The user cant be found by any means h3. Workaround No workaround available |
New:
h3. Issue Summary
User picker in "Request participants" field cant find the user by their email address ({*}or any other attribute{*}) when the user has a very short name. Example: !image-2023-01-24-17-05-45-332.png! - Edit an issue and try to add the user as a Participant using its email address: !image-2023-01-24-17-18-32-827.png! - The user can't be found by email, full name or shortname h3. Steps to Reproduce Not possible to recreate h3. Expected Results Find the user at least by their email address h3. Actual Results The user can't be found by any means h3. Workaround No workaround available |
| Introduced in Version | Original: 9 | New: 4 |
| Support reference count | New: 1 |
| UIS | New: 2 |