nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA Saved Filters Lose Their Boolean Groupings

terryaney

I'm trying to save a filter as the following:

(status in ("To Do", "In Progress", "Publish To Live") AND (assignee = currentUser() OR assignee = btr.users)) OR (status in (Review) AND reporter = currentUser())

After clicking save, the filter/jql remains correct, but if I leave the page and come back to the filter definition, it loses the parenthesis and presummably changes the results/meaning of the query. After coming back, the filter looks like this:

status in ("To Do", "In Progress", "Publish To Live") AND (assignee = currentUser() OR assignee = btr.users) OR status in (Review) AND reporter = currentUser()

Any advice on how to preserve the filters would be greatly appreciated.

Accepted answers

JamieA

> and presummably changes the results/meaning of the query

But does it? As a quick check you can just see if the same number of issues are returned for both queries.

If they are different, looks like https://jira.atlassian.com/browse/JRA-39107.

All comments

Eric Mathiasen

I've seen this, too. I don't have a solution, but just wanted to pile on to say I've experienced this problem as well.

JamieA

> and presummably changes the results/meaning of the query

But does it? As a quick check you can just see if the same number of issues are returned for both queries.

If they are different, looks like https://jira.atlassian.com/browse/JRA-39107.

terryaney

Think you are right...answering myself below but giving you credit.

terryaney

I think I might have just panicked at first look, but from my quick batch of tests, both of the following always behave the same (correctly).

var toDo = false;
var assignEE = false;
var toReview = false;
var reporter = true;
( ( toDo &amp;&amp; assignEE ) || ( toReview &amp;&amp; reporter ) ).Dump();
( toDo &amp;&amp; assignEE || toReview &amp;&amp; reporter ).Dump();

JamieA

Now I'm really confused. What you've posted there is about operator precedence, and yes generally AND is higher than OR. But that's nothing to do with JQL, which the docs say is parsed L to R. What is this code exactly?

terryaney

Well, this is just showing that my conditions evaluate to the same regardless of the nested parenthesis. So, I guess I'm saying/hoping that there isn't a problem with JQL in terms of not keeping nested parens, but rather it was 'smart enough' to realize they weren't needed and just saved appropriate query. Hopefully JQL isn't simply L to R and does obey order of operations correctly... - PS, this 2 comments per 24 hour limit force by JIRA is hard to work with

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

jql