Still no interest in fixing this?

It’s honestly beyond comprehension how an issue as critical and dysfunctional as this one hasn’t gathered enough interest or priority for Atlassian to address. A knowledge base without a proper search function is a contradiction in itself—what’s the point of storing information if users can’t efficiently retrieve it?

Customers have been reporting this problem for years (some tickets dating back to 2016!), and yet, here we are in 2025, still waiting for a solution. At what point does Atlassian acknowledge that this is not just a minor inconvenience but a fundamental flaw in Confluence?

Meanwhile, I’m being harassed daily by my team and our clients over this issue—and honestly, I can’t blame them. Their frustration is justified. The stress this creates is enormous, and as an administrator, my position has become untenable because of this bug. I’m expected to provide solutions, but how can I when even Atlassian refuses to address a problem this severe?

Yes, alternative solutions are becoming harder to ignore, but the additional workload is massive—having to explore new tools while still maintaining our current system is overwhelming. And that’s not even considering the nightmare of data migration and the complete breakdown of Confluence’s integration with JSM. This situation is beyond frustrating—it’s unbelievable.

On top of that, chasing Atlassian support on this issue has basically become a part-time job—and it shouldn’t be. I shouldn’t have to spend my time constantly escalating this problem, nor should I be put in a position where I feel forced to discredit Atlassian’s products to my colleagues or even publicly on social media. That’s the last thing I want to do—but at some point, what other choice do we have if this issue keeps being ignored?

I also have an upcoming meeting in my company about this, and thanks to Atlassian’s lack of interest, I will look completely incompetent trying to explain why this issue is still unresolved.

Please, please, please—you HAVE to prioritize this and communicate with us. This is not a minor inconvenience. This is a critical failure affecting real businesses, real teams, and real people. We need answers.

ee1911a8f30a 505da7f6a08d cteh 7edc8bf2bf6d vsiqueira  nghuraiya@atlassian.com 

Countless customers are desperately waiting for this feature..
32b46f90b164 3a052eec4d4e 656b6a1af4e3 904def9d3719 c4a065a011ab 35513a0d2c6f afe1aaea869c 94914d852cbc 93dd6428171f 1c84a12205ac eb3858a0d143  ...

Happy New Year 2025!  

Though it’s hard to fully celebrate when we’re starting yet another year without any updates on this issue. It’s honestly baffling that a knowledge base—meant to empower users—still lacks a functional search feature.

At this point, it feels like we should start celebrating anniversaries of this bug instead. As paying customers, this lack of resolution is not only disappointing but actively impacts our ability to support our ~35 000 customers. A knowledge base without search is like a library without an index— or a car without wheels - what’s the point?

To make matters worse, my boss has been asking me for the past three months to consider analyzing a migration to Notion. I’ve resisted the idea because it’d be veeeery painful and time-consuming (particularly after the server-to-cloud migration six months ago), but at least it would work. Frankly, it’s becoming harder and harder to argue against it when this issue remains unresolved.

We truly hope this critical issue is addressed soon. After all, starting the year with unresolved bugs and frustrated customers isn't the most inspiring way to kick off 2025.

Just as a reminder, issues to vote:

• AI-910 created in 2016
• AI-900 created in 2021
• AI-348 created in 2020
• CONFCLOUD-45631 created in 2016
• CONFCLOUD-43592 created in 2016

505da7f6a08d 7edc8bf2bf6d 8cf5262db9b9 

We are also coming up against this issue in our environment. We use Confluence as an Internal knowledge base, as many others do and opening up pages to allow for anonymous access is not acceptable. An internal knowledge base absolutely needs a search function for any user given access.

Can someone form Atlassian please engage in this issue and provide an update?