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".
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,
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.
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?
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.
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...
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