Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Jira filter column search will not display all search results for field "Status"

My business has alot of custom fields with status is the name. When trying to add status to a filter column the search will say "27 more options. Continue typing to refine further." That doesn't help when we are searching for the jira standard field "Status".

3 answers

0 votes
Tyler Brown Community Leader Aug 31, 2017

Hey Duane,


When you are entering your query, you should just be able to type "status =" or "status in" and continue with the status you want to search for from there.

JIRA should detect that you're looking for the native status field.


Hope this helps,


Hello Tyler,


In this instance I am talking about adding a column for status and the the column search won't display all the search results to display Status as an option.



Tyler Brown Community Leader Aug 31, 2017

Apologies for the confusion.  Is there any way you could remove some of the custome fields or rename them?

You could also try hitting "Restore Defaults" under the search bar.  That will (I believe) bring back the Status column.



Unfortunately all custom fields are in use and the restore defaults does not bring it back.

If "restore defaults" does not get it back, then your administrators have changed the defaults.  You should get them to add the status proper back to the defaults.

I'm afraid that's one of the only two option now, recent UI changes have broken the work-around.  The other option is to address your "fielditis", as Tyler suggested - 27 status is probably around 20 too many.

Is there documentation on how to change the defaults on admin side? I have admin privleges but this issue still appears when searching under "system defaults" columns.

Not sure there's a doc, but it's pretty much the same place.

When you log in as an admin, go to the three tabs (My defaults, filter, system), and click system, then a "restore defaults" will appear for that (along with a warning that you may affect all users).  That will reset the system defaults completely.

Simple fix:  Show the items that "start with" the letters I type at the top!   Eg. It makes no sense to show 40 items that merely "contain" Status before the ones that start with status - like the word Status itself.  Its very frustrating- there's nothing more I can type.  I typed the whole word.  Hello?  

Like # people like this

I'm having the same issue. This is a terrible search experience. 

It is, but only for people who have broken processes that lead to a  perceived "need" for more than one stauts field.

Why have you got 40 fields with "status" in their names?

I am stuck too and came looking for an answer here, but seems there is no straight one (or possible none). I have worked a way around this by using a public query/filter which has a status field selected in it. I don't know how they managed it, but I simply tweak that existing query with my filters and make sure I DO NOT uncheck the status field. So far this has worked, but it is a big pain to have this done every JIRA project.


In an ideal world I should get all results when I search for keyword, irrespective of how many they are, just let me scroll to the very end and choose it. How difficult is that?

Indeed, it is a very bad experience.

Ideally, Atlassian could implement an allow to use REGEX expressions, so this issue will be gone automatically.

Besides, a tested workaround you could use is to remove some of the HTML option elements loaded in your browser (inspecting the HTML code) that has the name you want so you just shortlist it till the point you show it in the UI.

All the elements are placed within the select with "id=filter-column-sparkler"


Hope it helps.


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

Why everyone using Jira must be GDPR-compliant

Did you know that penalties up to 4 % of the yearly company turnover are possible in case of GDPR violations? GDPR regulations are currently mainly relevant for companies in the EU, but countries lik...

100 views 1 3
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you