nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can't add standard "Status" field to issue navigator

Liam Bottomley

This question was raised here. However the resolution is not satisfactory.

In the issue navigation (Issues>Search Issues), when trying to add the default field "Status" as a column to my table of results, I search "Status" I get the response of “33 more options. Continue typing to refine further.”

I cannot refine the search any further as I am looking for "Status" but the options presented in the list are various fields containing the word "status".

Suggestions made in the other question:

Remove the other fields with "status" in - This is not an option, they are in use.
Edit the HTML of the page - I have not been able to successfully achieve this, nor should I have to.

I'm not an admin.

Jira v7.2.7

Accepted answers

All comments

Nic Brough -Adaptavist-

Option 1 is still the right thing to do. You have "fielditis" and that's going to cause you other problems in the long run.

There is no "fix" for this, and as far as I can see, Atlassian have no plans to do anything about it.

Randy Wilson

What we are seeking is a workaround for those of us who have no control over the fields that get defined in a large organization. At a minimum, an exact match for your search should always appear at the top of the results.

Liam Bottomley

Nic, I do see the "fielditis" issue and it wouldn't be my way of working.

As Randy says, I have no control over the whole organisation, its a large multinational organisation (100,000+ employees) with a huge number of projects. I can see around 70+ Projects, plus there are those with more restricted access that I can't see.

It's unrealistic that I'll get so many fields removed - an exact match would be ideal.

I would be surprised if what Randy and I are experiencing is an edge case

Nic Brough -Adaptavist-

I'm afraid it probably is an edge case - Atlassian simply haven't had enough people complain to make it worth while going back to the previous UI (which had a workaround) or engineering something else that solves it. And their answer for a workaround currently is, sadly, pretty much just "fix your fielditis"

Parthiban Thilagar

May be someone has already stated this already.

If I am allowed to create a new field with a unique name, all of us with access to that data should then be able to use that name to retrieve and view the contents of that field.

Thanks to Mark Diamond for the work around. However, this should not be treated as an edge case requiring a work around or a hack at the end user level. Most of our end users cannot handle this.

Ryan Bullock_1cnnlc

+1 for a permanent fix for what seems like a simple problem. In our case it's not the word 'Status', but 'Type'

Fielditis is certainly a factor, however designing a user-friendly interface is important as well. As people have noted, it's not the easiest to control fields across an entire organization.

Nic Brough -Adaptavist-

It's much the same answer - if you have 25 "type" fields, you've probably got 20-24 too many. Are they all really going to useful in reporting? Do your people actually use them all correctly? Obviously, you're not in the slightest bit Agile, but is your Waterfall process doing what you need?

roger.owers

Came across this again this morning, wasting hours of my day, finding the html to fix, can you please just allow an exact match to appear at the top of the column chooser? I just want to use the system, the custom fields are out of my control, this really is awfully painful.

Nic Brough -Adaptavist-

There is not going to be any fix for this in the code for the foreseeable future. Your only proper fix is to beat up your admins to fix your fielditis problem.

Filipi Lima

Hi all,

This is a suggestion that would address this and has the most votes and attention. Add your vote there as well if it affects your team.

See more available fields for Columns in Issue Navigator without typing

Cheers,

Filipi Lima

harryb888

Thanks - I voted. JIRA has been open since 2016...

roger.owers

Voted, although I feel it is pointless

Ed Jones

Ditto.

I does feel like the whole issue is being over thought.

Let's assume that massive organizations are never going to (be able to) fix their fielditis. And, let's not forget; Jira _allowed_ us to get into that state, which they so decry.

The simple fix is just to change the "X more options. Continue typing to refine further." text to a link that says (something like) "X more options. Show all."

As I've said before; the options are _already there_ in the HTML, we just need an easy way to see them!

Melissa_4kj7fr

I am shocked to find this is still an issue after so long! I am not administrator or even the project owner. We have lots of teams with lots of statuses and possible (I can't see them) lots of custom fields.
All I want to do is add a filter so that I can see anytime the status is not in or in certain states. And yet each time I try to build a custom filter for this the status piece never works. As far as I can see the column is just called 'status'. There are no other options or names available to me.
Please, please resolve this. It's such a minor thing but is making life finding all my tickets I am not assigned to very difficult when there are hundreds of Done ones and I only want the non-Done status ones. Thx.