-
Bug
-
Resolution: Not a bug
-
Low
-
None
-
Severity 3 - Minor
Summary
When doing a user or group search to set Permissions on a page, the results are not reflecting the search pattern when the search has a space. Example: A search for "test j" will return the same results as "test" without considering the space or the letter "j".
Problem:
If the site has more than 6 users with the same name but different last name, the searchable user may not be listed at all, and incorrect users will be listed
Environment
- Confluence
Steps to Reproduce
- Create at least 7 users with the same first name but different last names
- Search for the 7th user using the Last name initial
Expected Results:
- User is listed because it is matches the search.
- Other users not matching the search pattern are not listed.
Actual Results:
User is not listed at all
the user "Test Jk" exists and should be listed.
The search is triggering the call:
https://site.atlassian.net/wiki/rest/prototype/1/search/user-or-group.json?max-results=6&query=test+j&_=1492998751784
that returns the same results as "query=test" and don't include "Test Jk" because it is limited to 6 results.
Notes
Searching with the first 2 letters of the last name will return the correct results
User mentions on pages and comments are not affected because they use a different rest api call to get search results.
Workaround
Search for more than 2 letters for first and last names.
- relates to
-
CONFCLOUD-43226 Auto-complete and Group name picker limit in page restriction
- Closed
[AI-294] User and Group search doesn't return correct results for 1 character after space
Component/s | Original: Search - Indexing [ 46493 ] | |
Component/s | New: Search - Indexing [ 75295 ] | |
Key |
Original:
|
New:
|
QA Demo Status | Original: Not Done [ 14330 ] | |
QA Kickoff Status | Original: Not Done [ 14234 ] | |
Affects Version/s | Original: 1000.122.1 [ 68106 ] | |
Project | Original: Confluence Cloud [ 18513 ] | New: Atlassian Intelligence [ 23110 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2365947 ] | New: JAC Bug Workflow v3 [ 3402979 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 2239954 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2365947 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2200930 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 2239954 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2135408 ] | New: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2200930 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 2012358 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2135408 ] |
Resolution | New: Not a bug [ 12 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Link |
New:
This issue relates to |
Status | Original: Needs Verification [ 10004 ] | New: Open [ 1 ] |
This happens by design. The user fullname is on a "leading edge bigram" analyser. The name "John Smith" will be searchable only on "Jo", "Joh", "John" and "Sm", "Smi", "Smit", "Smith". The one character case is ignored since that creates too much noise in the results for most other cases.