Advanced Search and Custom fields

I want to create a filter that searches for all empty assignments.  I use a Group Assignment custom field as well as the normal person assignment field.    So I only want issues that are empty in both  assignment fields.  

I'm using this but it is being rejected by the search filter.  Any way that I can form the search correctly?

 

status in (Open, "In Progress", Reopened, Resolved, "On Hold", "To Do") AND assignee in (EMPTY) AND "Group Assignee" is EMPTY

 

3 answers

1 vote

Rick,

When you mention:

it is being rejected by the search filter

Is there any error messages returned? Please share that with us. smile

Also, are you using any context for the custom field "Group Assignee", such as restricting for certain projects or issue types only?

No response.   I "save as" the the revised filter and when that is done it has removed the last part of the filter query..So it comes back as "status in (Open, "In Progress", Reopened, Resolved, "On Hold", "To Do") AND assignee in (EMPTY) "

 

 

 

Just to be sure, after you are adding "AND "Group Assignee" is EMPTY", did you run the filter? So, let's say you have a filter, you open it, edit it, you need to run it before you are able to save the modifications.

0 votes

Hi Rick!

Normally, when you add new Custom Fields (or make changes other sections that deal with searches), you may have to re-index JIRA. Have you performed a re-index after adding those fields?

Cheers!

Joao

Yes and just did the reindex again same result

0 votes

You've got 

status in (Open, "In Progress", Reopened, Resolved, "On Hold", "To Do") AND assignee in (EMPTY) AND "Group Assignee" is EMPTY

Which looks slightly wrong to me - specfically "assignee in (empty)" doesn't have the right ring.  Could you try

status in (Open, "In Progress", Reopened, Resolved, "On Hold", "To Do") AND assignee is empty AND "Group Assignee" is EMPTY

(Oh, also try "assignee = unassigned" - that might be better too)

assignee in (EMPTY) is correct according to JIRA Auto JQL generator. I think it maybe related to indexing :)

Although assignee = unassigned would likely be better performance wise, they both are the same as far as the results they'll bring. As far as index related, that shouldn't be the case, otherwise the filter would be saved, just would not return anything. :/

And he said he just re-indexed :p

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,413 views 15 19
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you