-
Bug
-
Resolution: Fixed
-
High
-
7.1.10, 7.3.8, 7.4.4, 7.2.11, 7.6.0, 7.5.3
-
7.01
-
7
-
Severity 3 - Minor
-
17
-
-
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
- 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
- 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
-
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...