CONF-30698, CONF-11750, CONF-34892 are all for the same request, please add full path in search quick search and full search result page.

I am also very interested in this being an option again. I'm currently implementing several different content types that represent entities from our CRM. They are searchable, but I would really like there to be a way to customize the search results.

My use-case that's making me actually ask for this:

I have contacts that are being imported into Confluence from our CRM. At first I made the body of the custom content type empty and the search results appeared fine, albeit almost useless without clicking into the entity and going to the entity page. I wanted to add the most useful information to the results listing: phone number, email address link, title. For now I just added it to the body of the custom content type, but as it renders as normal, all the line breaks and HTML are removed and an ellipses cuts off part of the contact's title.

I'll make due with it as-is, but it would be really useful to have the ability to provide a custom Velocity page or something that results of a certain content type could use to render.

We are also very interesting on a solution for our plugin Scroll Versions and Scroll Translations to optimize the search result in terms of different page versions, translated content/title, etc. I assume the new content properties would help but we have to support Confluence 5.3 and newer.

aribrown,

There is a slightly useful feature here, despite the raw JSON diagram content which you see when clicking directly on a Gliffy search result. It's possible to navigate to a diagram's parent/container page by clicking the light-gray text link that's below the page content in the search results (next to the page's last modified date). This somewhat useful feature is why we haven't yet removed ourselves from the search results entirely. However, I understand your complaint, and we would love for Atlassian reintroduce the SearchResultRenderer so we can provide a nicer experience.

Regards,
Mike Cialowicz
Atlassian Ecosystem Lead
Gliffy, Inc.

My issue at present is that without this renderer, the Gliffy diagrams are included in search but returned as JSON garbage. I can't exclude them from search by default, as far as I know...

Dear Mike

Thanks for raising this issue. SearchResultRenderer was removed due to performance reasons. The advised way for handling this is to ensure that the index contains human readable description of the searchable content. I will leave this issue open so we can gauge interest in finding a way to reintroduce the feature in some form.

Regards
Olli Nevalainen
Confluence Bugmaster
Atlassian