Charlie Marriott added a comment - 27/Jan/2021 12:23 AM Atlassian Update – 27 Jan 2021 Hi, Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here , and how we prioritise what to implement here . To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues , and current work and future plans . Regards, Jira Service Management, Server & Data Center

Tanya C added a comment - 06/Dec/2020 10:21 PM I host several Jira Data Center with 2000 projects and several Confluence DCs and Servers (5000+ projects spaces) In several cases my customers would like to remove the search bar to force users to the forms listed. Sometimes there may be only a few forms and the JSD may not be connected to a KB.  They just don't want the search at the top of the portal. In other cases we have KBs that are joint usage.  They contain: Content related to the specific service requests; Public content that is more related to release note; general information; or Reports etc.  The customers don't want to maintain two or three Confluence spaces so all content is co-located. In this situation when a user enters a string into the Search field of the JSD portal home ALL content is searched NOT just articles relating to the service portal. The ability to 'Show Search' or 'Hide Search' would solve case 1 but for case 2 we would like to use a label or labels to limit content searched there. I feel both are easy fixes and code re-use configurations that could be added to allow more flexibility in setting up a JSD.  Not all JSDs are created equal and they are being used in creative ways more and more, especially with respect to KB information.  ... Not just the single minded way that Atlassian's may think of how they are configured or used.   Thanks for asking the 'why' to gain more information about real life usage of JSD. Cheers - Tanya Baltimore Atlassian Community Leader