Jira Filter - Cannot Switch Back to Basic View

[Eleni DeBord]

Hello!  I attempted to make a simple edit in my filter, by removing an Epic Link.  I did not save it and simply hit search to run.  It comes back with some message that a certain epic does not exist and does provide the name.  The problem now, is I can't switch back to the "basic search" to edit, or add back, etc..  I get a message, that it's too complex?  Not very complex as I'm simply filtering on Project Boards and Epic Links (IN).  So, my question is how can I back to the basic view?  I don't see that epic link in my query code via JQL.  So, I can't really edit anything from there.  Now, when I run, I get nothing but that error.  The strange thing is I never saved it, yet it saved automatically some how.  Is there anything I can do on my own to resolve, or will I need a Jira Admin to correct, restore, etc..?  Is there a way for the Jira Admin to restore at all? 

Thank You!  Eleni - The Home Depot

[Walter Buggenhout · Accepted solution]

Hi @Eleni DeBord and welcome to the Community!

If there's an "OR" somewhere in the JQL, that may be one of the reasons why you can't switch back to basic. It does not necessarily need to look complex for the basic filter to become unavaliable; just adding one thing that is not supported as a feature is enough.

Hope this helps! If not, sharing your exact filter here might help us help you!

[Eleni DeBord]

Thanks so much!  I think my one issue is more of security issue now.  Not having access to view.  I will most definitely share my SQL, if this does not resolve the issue.  :)

[Eleni DeBord]

I can run my query now!  It looks like it was more related to listing an Epic that was not in a Project board.  So, maybe it was a little too complex.  Anyway, I did not have access to view that epic.  All set and again, I appreciate your help.

[Craig Nodwell]

Hi @Eleni DeBord welcome to the community.  As soon as you add an "OR" to a filter it is no longer considered basic.  You should be able to edit the filter in the advanced view, it sounds like it is looking for an Epic that no longer can be accessed.  Removing that reference from the filter should remove the error.  And no if you are the owner of the filter you should not have to get an admin to fix it for you.

[Eleni DeBord]

Hi there and thanks for your quick response.  I'm actually not using the "OR" syntax, just "AND".  I did remove the one epic and my other issue appears to be security related.  So, maybe I will be able to correct.  

Thank You!  :)

[JJ]

Having the same problem using this query (also no OR): project = LFS AND status != Done AND due <= 3w ORDER BY resolution DESC, created DESC. 

Doesnt help if I remove the ODER BY...

Any idea what I can do? 

[Robert Leachman]

JJ one of my users has asked for help on the very same thing today. The problem we are having is "status != Done". It seems that in Basic mode the only option is to select all the statuses that are not done.

The issue I have is that this approach is not future-proof. If we later add another status "In Progress But Tricky" the filter would not find these non-done tickets.

HTH!