standard predefined filters - replace resolution with status

I adjusted my issue view and also removed the resolution field because I use the status indicator for this

Unfortunately the standard filter on the Board is link as follow:

assignee = currentUser() AND resolution = Unresolved order by updated DESC

which comes to the error Field 'resolution' does not exist.

I would like to change this to 

assignee = currentUser() AND status = Open order by updated DESC


Could you please tell me where I can change this. I played around with the Filters, but I can't access/change the upper 9 standard predefined filters.





2 answers

Hello Stefan,

I am afraid  it is not possible to change predefined filters. However, you can create your own filter and use it and maybe that could be the way to do it.

Could you please specify, where do you need your updated filter?


thanks for your answer.

Those are the standard filters, which are on the browse issues window (http://.../issues/?jql=).

On the left side of the issue overview.

1 vote

>also removed the resolution field

Do not do that.  There are vast amounts of places that Jira uses the resolution field, not just the system filters.

You absolutely must have the resolution field available for all issues.  If you don't want the users to set it, that's fine, you can remove it from screens, but you must set it in the workflow for them, or things stop working the way people expect them to.

Thanks for your answer.

If the resolution field is required for the system, it should be a mandatory field which is not possible to remove. Which is not.

Especially the Dashboard "My Issues" is also connect with this and not changeable in the setting of the Dashboard.

I added it again and works now.



You absolutely don't want it to be mandatory!  That would also break everything.

You are right, it should not be listed in the field configuration at all, so no-one can remove it.  There's an improvement request logged to get it taken off the field config stuff.  Although we're all hoping that field configurations are thrown away soon, with functions moved to more appropriate places.

I'm happy that's NOT mandatory and now only a "useless" field.



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,774 views 18 21
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