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; } } }

Board JQL Query

Jack Tucker

Hi Guys,

Just wondering if anyone else has encountered this and found a work around .....

My JQL query for a board reads as the below, the board is unable to see "Projects in board" when the cascade option for the JQL query is empty. I have highlighted the part in bold I need to remove in order for the board to see the projects in the board.

project = "First Responder Inbox" AND "Group Assignment[Select List (cascading)]" in cascadeOption("Bank Payment Network",none) OR "Group Assignment[Select List (cascading)]" in cascadeOption("Bank Payment Network", "Merchant Engagement")

Screenshot 2023-07-28 at 08.54.51.png Screenshot 2023-07-28 at 08.56.07.png

Appreciate any help on this! Thanks!

Jack

Accepted answers

Jack Tucker

Hi Guys,

Thanks for all the responses, I think I found a fix for this (not sure why this works tho)

Turns out specifically specifying the project again after the first part of the filter allows the filter to pick up the project, I changed the filter to the below and it now works.

project = "PDFR" AND ("Group Assignment[Select List (cascading)]" in cascadeOption("Bank Payment Network",none)) OR project = "PDFR" AND ("Group Assignment[Select List (cascading)]" in cascadeOption("Bank Payment Network", "Merchant Engagement")) ORDER BY created DESC

All comments

Dave Mathijs

Hi @Jack Tucker

I don't know what you're trying to achieve with the filter but could it be that the JQL needs to be:

project = "First Responder Inbox" AND ("Group Assignment[Select List (cascading)]" in cascadeOption("Bank Payment Network",none) OR "Group Assignment[Select List (cascading)]" in cascadeOption("Bank Payment Network", "Merchant Engagement"))

This will give you issues from project First Responder Inbox where the Group Assignment is one of the options provided (within that project only).

Jack Tucker

Hi Dave,

Thanks for your reply, I am trying to get the filter to show issues where the option is Bank Payment Network and the cascading option is Merchant Engagement, but also when the first option Bank Payment Network is selected and the cascading option is empty.

When I have this part in the filter it is unable to see the project:

("Group Assignment[Select List (cascading)]" in cascadeOption("Bank Payment Network",none)

Many Thanks

Jack

Marc -Devoteam-

Hi @Jack Tucker

I might have found the issue in the JQL.

The cascade option none has to be specified with quotes as well and to keep the OR clause in the project First Responder Inbox, also include this clause in ()

Can you try the JQL?

project = "First Responder Inbox" AND ("Group Assignment[Select List (cascading)]" in cascadeOption("Bank Payment Network","none") OR "Group Assignment[Select List (cascading)]" in cascadeOption("Bank Payment Network", "Merchant Engagement"))

Nic Brough -Adaptavist-

That will only work if there is a "none" option in the field.

Experienced Jira admins will never add "none" as an option.

Isaac Van Baren

@Nic Brough -Adaptavist- saw your reply to my question in another thread, and clicked your name to see recent activity. This question popped up, with your answer highlighted... And it caught my attention, because I was literally in the middle of adding the text "None" to some custom fields I had made. Will you please explain why this should never be done?

Nic Brough -Adaptavist-

So the simple human answer is "because it is a confusing lie".

If you add "none" as an option to a select list, then it is lying when people see issues with that value. "None" as an option is a value, so it's telling people the wrong thing.

The key thing here an understanding the difference between an empty field and one with data in it. Humans don't handle blank data very well, so most systems display something like "none" when the field is actually empty.

The problem with adding "none" as an option is that it's

A contradiction in terms - it says none, but that's a value, so the field is not none. If you add and use a "none" option, then your searches will fail when running "and field is empty"
Confusing - as Jira offers "none" as the option to select when you want to blank out the field, you will end up with two "none"s on the list and no indication of which is which

Jack Tucker

Hi Guys,

Thanks for all the responses, I think I found a fix for this (not sure why this works tho)

Turns out specifically specifying the project again after the first part of the filter allows the filter to pick up the project, I changed the filter to the below and it now works.

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

jira-software-cloud