Details
-
Bug
-
Resolution: Not a bug
-
Medium
-
5.1.3, 5.3.4, 5.4.2, 5.4.3, 5.4.4, 5.5, 5.5.2, 5.5.3, 5.5.6, 5.6.1, 5.7.1
Description
Other than stated in the help for the search, wildcards used at the beginning of a word don't work.
We are using Confluence 5.3.4, but this seems to be true for 5.4.3 as well.
This might not be an issue for many users, for us this is unfortunately a major drawback, as we use confluence to store technical documentations and make them available and we have conventions where only the first characters of names/terms differ and where we need to find all pages relating to such terms.
E.g. we need a search like "?0DUMMYXY" or "*DUMMYXY" to list pages relating to terms like 10DUMMYXY, 20DUMMYXY" etc.
Steps to Reproduce:
1. https://confluence.atlassian.com/display/DOC/Confluence+Documentation+Home
2. Search "confluence"
3. Yields 884 results (correct)
4. Search "c?nfluence"
5. Yields 884 results (correct)
6. Search "c*nfluence"
7. Yields 884 results (correct)
8. Search "?onfluence"
9. Yield no results (incorrect)
10. Search "*onfluence"
11. Yield no results (incorrect)
Attachments
Issue Links
- duplicates
-
CONFSERVER-37063 Leading Wildcards are not working, * and ?
- Closed
- is duplicated by
-
CONFSERVER-36510 Wildcard search doesn't work as documented
- Closed
-
AI-411 Search results with wildcards is not complete
- Closed
-
CONFSERVER-33631 Wildcards are not work when used the beginning of the string.
- Closed
-
CONFSERVER-34245 Wildcard search does not work when using in the beginning of a String.
- Closed
- relates to
-
CONFSERVER-33120 improving german solrlucene search results
- Closed
-
CONFSERVER-37153 Confluence Search: Wildcards at the beginning of a word do not work
- Gathering Interest
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- Wiki Page
-
Wiki Page Loading...