nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Differences in search in Confluence

KMTek

Hi,

We recently installed Confluence 7.13 Server and notice that now we need to write an entire word or use wildcards in the quick search to have some matching results. In previous versions all we needed to do was writing the first characters of the term being searched and the results would start showing up.

Is this the way we use the syntax for the search in Confluence 7.13 , or did we miss something while installing and configuring the platform?

Thanks

Accepted answers

Brant Schroeder

@KMTek

It should begin looking a soon as you type any character into the search. I believe that there are some characters like the letter a that it will not search for until additional letters are added. What characters are you using?

Additional search information can be found here: https://confluence.atlassian.com/doc/confluence-search-syntax-158720.html

All comments

Brant Schroeder

@KMTek

Additional search information can be found here: https://confluence.atlassian.com/doc/confluence-search-syntax-158720.html

KMTek

Hi @Brant Schroeder ,

Thanks for your reply.

It happens mostly on pages classified with a prefix, such as QA001 or LTT036. In the first case, when the Q and the A are written a list of suggestions is shown dynamically, but when the first zero is entered there are no more results till the end of the prefix. Then it will display the page related with that title as the first result.

But it also happens with other words, like Poland, Romania or Germany. It's only at the end of these words that we receive some significant results, especially the pages with those titles that are never displayed till then.

In version 6.13 users are used to write the first three to four characters to have relevant results and this becomes now a big nuisance to them. The funny thing is that if we add the wildcard * after writing three or four characters we receive the relevant results we were expecting (eg. germ* will result several pages related with Germany, but nothing relevant if we use only germ).

Thank you

Brant Schroeder

@KMTek

I am able to recreate the issue so Atlassian must have changed the way that the search filter works between versions. I would suggest opening a support issue with them to see if they can provide any insights.

KMTek

Thank you Brant. We are going to do that.

Cheers

Robby Holtmann_IntraFind Software AG_

Hi @KMTek,

if you want to have more comfort in the search, you might also be interested in our solution iFinder Confluence Search. This enterprise search solution delivers top results based on linguistic analysis and offers many additional features. These articles may help you:

Cheers

Robby

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

server

confluence-server