Hi all, as a result of the improvements we've made to Confluence search over the past year (including semantic search) we've tested and believe this ticket is now fixed

Having the possibility to search partial strings and have accurate results is absolutely essential in a documentation tool. Our company is currently migrating a large documentation base in Confluence and our teams are deeply concerned with the loss of search capability. For example, it should be possible to do a search for 'inventory' and have the page containing the term 'warehouse.inventory' appear in the search results. Currently there is no way of doing that, which is basically crippling our capacity to search technical terms over a large number of pages. Please address this issue as this could (and should) make customers reconsider using Confluence as a reliable document management solution.

Correcting this would help user avoid being misinformed by search results that are not correct.

There is a workaround for doing wildcard searching at the beginning. If you structure your search like this ....

/.*hum.*/

... then you will get results for hum/human/inhumane/thumbprints/etc. The slashes tell the search engine to do a regular expressions search as opposed to a normal search. The .* before and after the search term tells the regex engine that you want any character zero or more times (in essence a wildcard).

We need to be able to search through our articles placed in Confluence. It's critical for us to have an option to index the part of code. For instance: when you have something like this "verify(api, times(1)).addOrUpdate" on the page, then you cannot find string "addOrUpdate" - it is not indexed.

It would suffice for us if words were separated by punctuation marks.

You would find the target by searching for ss_stored_procedure* - wildcard search is implemented.
But what not is working for years is a wildcard at the beginning of the search-string, although it is documented that it should work.

This is very painful that confluence doesn't support partial text searching. For example, we use confluence to manage code releases, and we put file names in like ss_stored_procudure.sql - but searching just ss_stored_procedure returns nothing... Like everyone else, we're happy with a performance hit for this, but it should be optional.

Out of interest, how many votes does something need before Atlassian looks at it?

+1

+1 for substring-searches for body-text:

This should be standard. Please implement this. Like others have said let your customers decide if it is something they want or don't want. We want it and would probably be willing to deal with any performance issues ... assuming the performance impact isn't so drastic as to make it unusable.