-
Suggestion
-
Resolution: Unresolved
-
Any
NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.
Our Confluence installation has around 150 spaces. Many of our users complain that "Quick Search" defaults to searching in all spaces, which makes it somewhat less quick since users always have to limit it to specific space searching.
I realise that many users with smaller Confluence instances would not mind this behaviour so can we have a site-wide configuration option to configure whether quick search searches the current space or the global installation?
It would also be very handy if there was a user preference that allowed the user to configure quick search behaviour on the home page - to specify either global search or limited to the user's favourite spaces.
- is related to
-
CONFSERVER-5338 Make quick search scope a site configurable option
- Gathering Interest
-
CONFSERVER-98809 Make quick search scope a site configurable option
- Gathering Interest
- relates to
-
AI-844 [search] smart search like in jira to limit scope to a space
- Closed
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
I have contacted Atlassian support about this issue today. I add it to this issue to maybe get more attention to the issue.
We are using Confluence Cloud for public user documentation. Our public site have several spaces. We want the quick search box (top right corner of screen) to return search results for the current space only as default. The reason is to avoid confusing the users of the user manual with search results from other spaces of the site, for example the technical documentation.
Yes, I know about the Livesearch macro and have used it, but the users keep using the quick search box and complain that they can't find what they are looking for because they get all kind of results they don't understand. I also know that you can filter the search in advanced search, but the users don't understand that.
A possible workaround for us is to have one site for each space we want to limit search for but this will cost more and could be an administration nightmare.
Although our use case is for external (anonymous) users, I believe it is valid for any space and users.