We're on Confluence Data Center 7.13.2 and AFAIK this feature does not exist in the top level search options at all.  So it seems like this feature has regressed. 

The ability to filter out personal spaces by default, much like we can with archived spaces, would make this product infinitely more useful.  It also seems like a very straight forward feature to expose and gives clients an opportunity to address a large usability issue in the Confluence through data governance, rather than having Atlasssian completely reinvent search.

From what I understand, this feature was restored in Confluence Cloud already, we would like it restored in Data Center as well

I would really like the ability to exclude Personal Spaces from Quick Search, or as mentioned in olde CONFSERVER-9927, have it be a configurable option.

In contrast to that bug's description, we have a lot of duplicate, non-canonical information in personal spaces that we would like to EXCLUDE in quick search.

@adam ahh, yes, my fault. I viewed this too fast and thought the issues was referring to restoring a feature for the quick search/suggestion links that get shown. I see that this is for the full search functionality. Thanks for the clarity.

Hi, in Confluence 5.9 we introduced CQL to search, this gives users the ability to choose 'Site Spaces', 'Favourite Spaces', 'Personal Spaces' or individual spaces.

I believe that this would provide/restore the functionality that this suggestion is referring to. I am just checking here as there seem to be quite a few comments recently. Could it be that you are on versions before 5.9, not aware of where to find the functionality, or otherwise?

+1

If I may make a comment ... Atlassian needs to do a better job of things like this.

1. This was an important feature that used to be in the product, that then disappeared.
2. By important, I mean that spoke to the heart of a chief complaint about your product ... "I can't find anything".  The removal of this feature diminished  the product in a non-trivial way.
3. Even worse, the documentation for the product still touted the feature, which only emphasized that it used to be there.
4. When this was pointed out by customers, rather than add the feature back in, they just removed it from the documentation!
5. Two and a half years later, the feature is still unassigned.

+1

Yup, I have CS staff that create their own pages in their Personal Site that mirrors a lot of information in our documentation (typically they do it to reinforce their own learning). These absolutely need to be excluded from search in certain places as we've had a few instances where someone has provided a link to a person space page to a client, the client has they called us up and complained about not being able to log in to access the content (all of our client facing documentation is Anonymous access so they should NEVER log in).

Linked ticket to CONF-33161.

This is annoying for us as well. Personal spaces that don't contain pertinent info but simply have a matching word often jump to the top of our search results now and it's a pain.