Yes jason.clark2 it's poor isn't it.
You watch - won't be long and there will be a rebadging of the plans/levels and you can guess what will happen the standard plan....

So to fix, what is potentially a security issue, we need to fork out another $30 per user?

Thanks cea8b6bddbc3 - that is great. I didn't realised with the customization that that banner could be hidden ... would be nice if we could just hide the search box. But I guess I can add an empty rich content in it's place.

Thanks again to you and Atlassian!

Update:

Hi Everyone! Just wanted to update here that we launched this capability in December 2024 for Premium and Enterprise Tenants on JSM.

It is now possible both reorder and hide the various sections of the Help Center home page, including the Top Banner that contains the Search Bar. Admins who would like to not have the Search Bar shown to their users can use this capability to have it removed from the view of their users.

Details below:

1. Announcement & Explainer Community Post 
2. Full Capability Walkthrough on Loom
3. Documentation Page

Warm Regards,
Raafi Mohammed
Senior Product Manager, JSM

adding a vote for this

Would also appreciate this change

Atlassians, I'll do this for you. Hand it over to me, I beg you! I won't charge you a cent, I swear, just out of the love in my heart (and to solve a huge, year-old problem I have because of this search bar). You don't even have to thank me or anything. In fact, I'll be the one thanking you!

Just sit back and relax. You won't have to shuffle developers around, risk missing any deadlines, nothing! Keep working on those great new features and let me worry about this one.

All I need is push privilege to a cloned branch of that Look and Feel right sidebar. I'll add a simple checkbox on top with a short message beside it (including translations). All you'll have to do is send it to your QA for testing and apply the boolean on the placement screen (which, of course, I can also do for you if you wish).

Please, allow me to help you guys out. It's my pleasure! Just let me know!

Surprised (and disappointed) this isn't possible. Using JSM for customer reported bugs should be a no-brainer for us, but the lack of basic configuration like this could force us to look elsewhere.

I would like to say I'm surprised that something so basic is not only not controllable but also actively poses a security risk yet has been like this for a decade, but sadly I'm not.

In fact, All Vivek Kumar did was update the description from 2021, by adding a more recent screen snap in the proposed solution. So then, JAC (this system), triggered the description update to all.

I think it was an accidental "update" email, and why would Atlassian send an update? They clearly don't care about this deficiently.

It’s been on long-term since 21/Oct/2015. 10 more years? 

300+ asking for this and 500+ watching this - don't you think it should be on your short-term road map?

How hard is it to hide a search bar on the portal? Also, the search is just not limited to the customer's portal project and shows documents across our entire instance. This is really unacceptable. Can someone please review this and get on roadmap ASAP! We all would appreciate it. thanks

Hi,

As recommended in duplicate JST-980651, I'm writing my comment here, hopefully not to all in oblivion, but my hopes are low...

Hi again,

Thanks for your answers, but what you suggest is not relevant to our case.

We actually have three projects, where only one should allow customers to get access via the portal.

In all the three projects, we need people to be able to create tickets, without being invited to priorly.

What we did, is that we hid the portals for the two projects where no portal access is required. Ideally, portal access should be disabled directly from within Jira for those two projects, but from what I understood, this is not possible (another breathtaking shortcoming by the way).

Thing is, if a portal is hidden, which is the case here, you evidently got a bug if the search bar allows you to see its contents, it’s a breach of security of major proportions.

So, here’s what we’re at:

1. Portal can’t be disabled on a per project basis from Jira admin

1. Having more than one project make the search bar visible on the portal and it can’t be disabled (let me reiterate that this is a 1 hour development, tops, we have already lost more of your time that it would take to solve this, just discussing this bug here)

1. You can hide portals on a per project basis (this is great)

1. The search bar allows a user to access info regarding hidden projects: this is a security breach, and would be considered as a critical bug by any serious ITIL company.

Ideally, 1. should be implemented, back office management should be the one stop shop to control it all, but I understand this would require quite a lot of development.

Then, as this would be discarded, the search bar should be rethought so it doesn’t allow to browse anything from the hidden portals, as again, this is a huge security breach. Unfortunately, this would require again some more development.

Hence, the simplest solution of all: keep all the search bar logic you want, and don’t change anything in back office, and just add a very little switch on the Edit home page layout, where the admins can decide to publish the search bar or not.

It would take any web developer literally seconds, and it would get rid of an issue that is nearly 10 years old and where you have more than 500 complaints.

For the life of me, I don’t understand Atlassian’s reticence to apply such a quick fix, even today.

I hope this clears up our need (and the rest of your 500+ users complaining on the daily).

Thanks in advance.

BR,

Seb

Especially as where it could be useful, it's buggy. When you enter a keyword corresponding to request types, it displays disabled request types instead of active ones, leading users to the error message 'page not found'...

It looks like this request for an obvious item was raised 9 years ago. Is it now possible to remove the search icon from the Support Portal page and if so how?

Hi,

Seeking another update on this.

Thank you.

Hi again.

Any update on this?

Please let us know what the threshold of comments is for you to act upon this BUG.  You got 500+ angry customers ready to fill the quota so you can solve this ASAP.

Thx

I found this because I wanted to remove the search bar. 

Hello,

Any update on this issue?

Is there an estimated time of resolution for this bug?

Hello,

Is there any update?

I can't believe that after 9 years, 500 comments are still in "review". I would recommend to those who are new to this problem to start developing their own website. I'm sure they will be finished before it is considered in the roadmap of the product, its completly abandoned.

Please try to enable this functionality. We want to be able to use this ticketing system effectively and don't want to leave Jira.

Continues to cause confusion within our team. 

How is this still open after 9 years???!

Agreed @69995a7d7b7f - We can see across few threads... there is consistent theme.....   bug/gaps get no focus from Atlassian.... it's all about new products and more $. 

I agree this is a security issue for our customers and other projects in use of the support portal. Please can this be escalated and placed as a priority on the road map.

Hi,

Enabling a switch to display or not a search tool would probably take less than an hour of programming and make a lot of people happy.  This Search bar is, to my view, nonsensical and induces confusion to the customers.  Worst of all: it allows researching help topics and access Request types from projects that have been hidden from the layout.

If a project is hidden and you can access it nonetheless using the help tool, this is not a suggestion or something nice to have.  This is a bug and needs to be fixed ASAP.

Could you please take one hour to create said switch, after all, this request has been created 9 years ago.

BR,

Seb

+1 we really need this functionnality please

I need it !!! I have several customers, several projects...

In my opinion, it is a security issue. Moreover it seems this feature is already available on DataCenter.

Pleeeeeaaaaase...

Fabien

Also requesting this - we have different customer types and they can search all kb articles using this search bar (unlike in space home pages where we can restrict search by label tags)

My Customers also need possibility to disable search bar, please implement.

Please add the option to make the bar optional, I don't want to use the knowledge base functionality, it's really distracting for our customers.

+1

+1  Please give the option to remove the search bar.

+1

+1

+1! Give us the option to turn it off, please!

+1. Please add the option to remove the search bar

Remove search bar please.

+1 our organization could really use a removable search bar.

+1 need option to remove the search bar also

Needed also. Thanks

We need this ASAP. We've got two portals with very different knowledge base articles and it's infuriating that this search bar searches across both portals and presents results from both. Also annoying that Confluence spaces from different projects keep linking back to the main help centre.

Needed. Please.

Hi 👋
in the Theme Extension app we have the possibility to hide/show and customize the Search bar on Customer Portal ✅

Optional Search Bar, please. Thanks

Just another barrier preventing adoption of JSM. 

I want to go live with portal ASAP, but transition customer knowledge base later.

I have to use an announcement to advise clients that the search box is a work in progress instead of just hiding the stupid thing. 

Remove Search Bar, please. Thanks

Do you guys now how many votes are needed to get things done? This request is from 2015 with no real follow up or any expected action.

The returned request type is limited and forced max 5 results! No way to change the max value. No reason for this limit and the search is useless. The Better Search in Customer Portal is better than the default search box.

Needed, please.

PLEASE CHANGE THIS!! That Search doesn't help me .

+1

This is very much needed change in our opinion - thank you

+1

I vote for this change.