Minor patch release for Jira Server 7.8.0 and Jira Service Desk Server 3.11.0 Released

A post to alert you all to a new minor release of Jira Server and Jira Service Desk Server.

Key things to keep in mind as a plugin developer

Stated in the Preparing for Jira 7.8 development guide is this suggestion for plugin developers to consider.

Quick search
What might be useful for plugin developers is monitoring how your users are searching and limiting the number of concurrent searches with regards to Quick search.

The quick search doesn’t affect performance in a significant way unless many users start searching at the same time. If you notice any slowdown, start monitoring the searches to find a limit that works best for your instance.

To monitor searching in real-time, use the quicksearch.concurrent.search metric in JMX. For more info on how to set up JMX, see Live monitoring with JMX.

Other considerations:

  • Oracle JDBC driver is no longer bundled with JIRA
  • Dutch language is now supported.

Release notes

Jira Core Server 7.8.0

Find the release notes for Jira Core Server 7.8.0 for more information on this minor release.

Jira Software Server 7.8.0

Find the release notes for Jira Software Server 7.8.0 for more information on this minor release.

Jira Service Desk Server 3.11.0

Find the release notes for Jira Service Desk Server 3.11.0 for more information on this minor release.

Released February 20, 2018

The quick search doesn’t affect performance in a significant way unless many users start searching at the same time.

Is there any option to disable the quick search?
I think some customers would like to disable this feature for performance stable.

Thanks.

Hey,

Quick search is bundled with Jira as a plugin, so you can turn it off by disabling the plugin. In ‘Manage add-ons’, find JIRA - Plugins - Quick Search, and disable it.

However, we don’t expect the default limit of concurrent searches (20) to cause any performance issues in most Jira instances. If it does, you can change the limit by modifying this global setting: jira.quicksearch.max.concurrent.searches

3 Likes

Thank you for your help!