Since cloud migration, our users just don't like using the Questions app due to the hassle (not exactly hard, but nevertheless, an additional page load that was not previously needed).

We're thinking of workarounds to this such as just replacing Questions with a space to try to make it easy to find the answers to commonly asked questions again. This might work with the right name formats and tags...

On-prem we did not experience Questions being in search results being an impediment to finding pages because they are generally commonly used, frequently asked things with a certain type of title that doesn't correspond to the types of titles most of our pages have. So while pages are more often searched, having Questions and Answers appear in the results didn't get in the way of finding content and was very useful for us.

We also find that Questions for Confluence is not very useful for our users since migrating to cloud with this behaviour.

In on-prem it was really useful as we use questions for quick but commonly asked questions and they would show up prominently and quickly in search results. So while pages are more often searched for, most of those don't start with "how" or "what" etc so questions don't typically pollute the search results when we're looking for pages.

In cloud, no-one wants to use Questions for Confluence any more because of the extra (not very difficult but cumbersome nevertheless) steps to quickly find the answers they want.

Elaine,

Would it be reasonable to make this a 'configuration' option w/ the default the behavior as is, so each customer can make the decision for their own use case(s).

The current 'behavior' will keep us from adopting Questions and we will keep using stackoverflow.

thomas.kramer, thank you for sharing your perspective here. I hear you that you expect questions to immediately appear in search results right away with the other contents.

Our current behavior is intended to strike a better balance between the relevancy and exhaustiveness of the default search results for the majority of use cases. Data showed that a large majority of searches were for pages/blogposts and spaces. If we include all content types in the default search results, the user is likely overwhelmed by irrelevant results and end up spending more time getting to what they need. A couple of extra clicks are needed to get to questions and other specialized content types. It's not perfect user experience but a worthy tradeoff.

It's possible that your use case is different in which question is the most sought-after type of content in searches on your Confluence site. In that case, I can see you prefer a different tradeoff. We'd like to learn more about how your organization uses Confluence and plans to use Confluence Questions and discuss how to best address your search needs in that context.

Thank you for your time,
Elaine Hankins, Confluence Cloud Product Manager

Dear Atlassian Team,

Is there any estimation about when this will be solved? We would like to roll-out this addin company-wide, however without integrated search this is not possible yet. It is very important, that questions are immediately shown as search results right away with the other contents.

Thanks & BR Thomas