Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Fixed
Priority: High
Fix Version/s: 7.8.2, 7.9.0, 7.7.4, 7.6.7
Affects Version/s: 7.1.10, 7.3.8, 7.4.4, 7.2.11, 7.6.0, 7.5.3
Component/s: JQL
Labels:
- pse-request

Fixed in Long Term Support Release/s:

Download 7.6
Introduced in Version:
7.01
Support reference count:
7
Symptom Severity:
Severity 3 - Minor
UIS:
17
Bug Fix Policy:
View Atlassian Server bug fix policy
Current Status:

Hide

Atlassian Update – 13 April 2018

Hi everyone,

The fix for this issue is available in 7.6.4, the forthcoming Enterprise releases and versions indicated above.

To prevent users from saving an empty filter unintentionally, we have implemented a warning message in Issue Navigator when a user is trying to save an empty filter. While editing an existing filter, users are expected to provide a validated query. The 'Save' button is inactive when the query field is empty or, the search hasn't been performed using the 'Search' button on creating a new filter.

Thank you,
Katarzyna Derenda
Product manager, Jira Server

Show
Atlassian Update – 13 April 2018 Hi everyone, The fix for this issue is available in 7.6.4, the forthcoming Enterprise releases and versions indicated above. To prevent users from saving an empty filter unintentionally, we have implemented a warning message in Issue Navigator when a user is trying to save an empty filter. While editing an existing filter, users are expected to provide a validated query. The 'Save' button is inactive when the query field is empty or, the search hasn't been performed using the 'Search' button on creating a new filter. Thank you, Katarzyna Derenda Product manager, Jira Server

Description

Problem

Jira has UX bug which is tricking users to save empty filter.

Scenario to trigger this bug:

Issues -> Search for Issues
Type JQL
Click save as and name the filter

Result

Empty filer is saved.

Expected result

Entered filter is saved

Root cause

This is happening because currently executed filter is saved not the one that is entered on the screen.
We suspect that this bug is creating problems with empty filters as people save them by accident not on purpose.

Note on fix

User will be able to save an empty filter. We just make user more conscious about what is saved by:

enabling save button only after search of entered query has been performed
providing a warning in case an empty filer is about to be saved
other minor fixes

Attachments

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

JRASERVER-66390-demo-part1.mp4
6.73 MB
13/Apr/2018 10:27 AM
JRASERVER-66390-demo-part2.mp4
4.03 MB
13/Apr/2018 10:27 AM

Issue Links

is caused by

JRASERVER-59571 As an User I don't understand which JQL is saved to filter

Closed

relates to

JSWSERVER-15051 Agile board with empty filter can trigger OOME

Closed

JRASERVER-65531 SingleLevelGroupByReport with Empty Filter Causes OOME

Gathering Impact

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

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

Closed

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...

(1 causes, 12 mentioned in)

Activity

People

Assignee:: Natalia Wroblewska

Reporter:: Adam Jakubowski (Inactive)

Votes:: 10 Vote for this issue

Watchers:: 20 Start watching this issue

Dates

Created:: 23/Nov/2017 8:51 AM

Updated:: 22/May/2020 8:23 AM

Resolved:: 06/Mar/2018 12:24 PM