As we are setting up a new Service Desk I'm experimenting with a Confluence knowledge base that is used when customers enter a new ticket. One of the things that I noticed is that the kb is searched on all terms used in the ticket. As this also includes frequently used words like "it".
Is there a way to "teach" the search engine to skip certain words? As almost every article in the kb will contain words like "it", "a" and "is" I'd like to prevent showing a lot of articles that have absolutely no relevance to the ticket.
You can use double quotes to search for a phrase that contains words like 'it', 'a' or 'is'.
e.g.: If you search for the phrase "confluence is a new way for teams to work together", the words 'is', 'a' and ‘o’ will be ignored.
As stated in Confluence's documentation: "Confluence will ignore common words (stop words), including 'and', 'the', 'or', and more, even if they are included within double quotes. See the default list of stop words used by Confluence's search engine, Lucene, in the Lucene documentation."
Thanks for your answer. As I'm mainly serving Dutch customers I'll be needing a way to manage those stop words as now they are in English.
Do you know if it's possible to edit the stop words in the cloud based version? And if not: do I have the option to do so in the server based version? We're still having to decide if we will use the server of cloud based version...
There is a stop word list containing Dutch words named "dutch_stop.txt". I guess it is possible to manage this list by following the instructions at this link: https://answers.atlassian.com/questions/37030881
Keep in mind that this workaround is valid only for server based version.
The story of our lives: "only for server based version". At the moment we are still considering the cloud based version and to be honest it only gets worse and worse. It's in the details but there are to many of them...
So if we can turn the management around and move to the server based versions we can continue with Jira but if not I guess there are to many details that push us to look for an alternative.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs