Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-65602

As an JIRA Administrator I want to make empty JQL return no data

XMLWordPrintable

    • 9
    • 9
    • Hide
      Atlassian Update – 13 April 2018

      Hi everyone,

      We're glad to announce that we've added an option to disable empty JQL queries in Jira general settings. This capability is available in Jira Software 7.9 released this week and will be available in 7.6.6.

      The new functionality allows Jira admins to choose how an empty JQL query behaves: either returning no results at all (ON), or all existing issues (OFF). We've introduced this option to avoid performance issues with empty filters returning all existing issues in your instance. The default state is OFF, since some plugins may be using empty JQL queries on purpose.

      An empty JQL query in Queues, SLAs and Reports within JIRA Service Desk will continue to return all issues per project.

      We have also added a UX fix for Issue Navigator to prevent unintentional saving of an empty filter. See JRASERVER-66390 for details.

      Cheers,
      Katarzyna Derenda
      Product Manager, Jira Server

      Show
      Atlassian Update – 13 April 2018 Hi everyone, We're glad to announce that we've added an option to disable empty JQL queries in Jira general settings. This capability is available in Jira Software 7.9 released this week and will be available in 7.6.6. The new functionality allows Jira admins to choose how an empty JQL query behaves: either returning no results at all (ON), or all existing issues (OFF). We've introduced this option to avoid performance issues with empty filters returning all existing issues in your instance. The default state is OFF, since some plugins may be using empty JQL queries on purpose. An empty JQL query in Queues, SLAs and Reports within JIRA Service Desk will continue to return all issues per project. We have also added a UX fix for Issue Navigator to prevent unintentional saving of an empty filter. See JRASERVER-66390 for details. Cheers, Katarzyna Derenda Product Manager, Jira Server
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Problem Definition

      Currently empty JQL returns all existing issues you have permission to.
      This might lead to performance problems at busy instance.

      Suggested Solution

      Add an option for JIRA Administrator to change to default behaviour of empty JQL, it will return no data.

      Workaround

      • Proactive - Check DB for filters with empty JQL. 
        select * from searchrequest where length(reqcontent) < 3 or reqcontent is NULL;
      • Check empty JQL ':' in logs, from atlassian-jira-slow-queries.log, eg: 
        2017-05-28 21:40:56,154 Caesium-1-3 INFO     [c.a.j.i.search.providers.LuceneSearchProvider_SLOW] JQL query 'order by updated DESC' produced lucene query '*:*' and took '2090' ms to run

2017-11-10 10:08:53,351 ajp-nio-8009-exec-3301 user INFO  608x29513053x25 1cx9voq /secure/ConfigureReport.jspa [c.a.j.i.search.providers.LuceneSearchProvider_SLOW] JQL query '' produced lucene query '*:*' and took '10353' ms to run.

        1. AVG response time for last 24 hours for 10m timespan.url
          2 kB

              mrydzewski Mikolaj Rydzewski (Inactive)
              ayakovlev@atlassian.com Andriy Yakovlev [Atlassian]
              Votes:
              5 Vote for this issue
              Watchers:
              25 Start watching this issue

                Created:
                Updated:
                Resolved: