Loading...

XML

Word

Printable

Details

Type: Suggestion
Resolution: Fixed
Fix Version/s: 7.2.14, 7.3.10, 7.4.7, 7.5.5, 7.8.2, 7.9.0, 7.6.6, 7.7.4
Component/s: JQL
Labels:

UIS:
9
Support reference count:
9
Fixed in Long Term Support Release/s:

Download 7.6
Current Status:

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
Feedback Policy:

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.

Description

Problem Definition

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

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.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List

AVG response time for last 24 hours for 10m timespan.url
2 kB
21/Nov/2017 12:34 PM

Issue Links

is duplicated by

JRASERVER-60233 As an Administrator I want to change default behaviour for Empty Search

Closed

is related to

JRASERVER-66390 It is extremely easy to save empty JQL filter

Closed

JSWSERVER-15051 Agile board with empty filter can trigger OOME

Closed

JRASERVER-65531 SingleLevelGroupByReport with Empty Filter Causes OOME

Gathering Impact

JRASERVER-66791 Make Lucene Search with unlimited PageFilter fail to prevent unnecessary memory allocation

Gathering Impact

JRASERVER-39542 Issue Navigator should default to no results for "New Filter"

Closed

relates to

JRASERVER-74270 Unable to calculate missing data in index when getting last issue update time returns null

Closed

JPOSERVER-2307 Filters yielding large issue result set can cause out-of-memory exception

Closed

JRASERVER-67409 Agile board based on JQL filters with empty WhereClause returns all issues even with 'Disable empty JQL queries' set to ON.

Gathering Impact

JSWSERVER-16546 As an JIRA Software Administrator I want to limit number of issues per board to prevent resource overuse

Gathering Interest

GG-9 Loading...

HL-7 Loading...

causes: PSR-57 Loading...

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

(1 is related to, 6 relates to, 1 causes, 44 mentioned in)

Activity

People

Assignee:: Mikolaj Rydzewski (Inactive)

Reporter:: Andriy Yakovlev [Atlassian]

Votes:: 5 Vote for this issue

Watchers:: 25 Start watching this issue

Dates

Created:: 12/Jul/2017 4:27 PM

Updated:: 02/Aug/2023 8:17 PM

Resolved:: 14/Mar/2018 10:05 AM

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

Details

Description

Problem Definition

Suggested Solution

Workaround

Attachments

Attachments

Issue Links

Activity

People

Dates