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; } } }

Showing custom fields in issue navigator when searching for multiple issue types

Magnus Haglund1

Is there anyway to workaround the limitation in the issue navigator that removes columns with custom fields that are not used by all issue types in the search?

(Not searching for just one issue type at a time and exporting to excel and then combine the excel documents)

Accepted answers

Jobin Kuruvilla [Adaptavist]

For simple search, no. Advanced searching doesn't have that restriction!

All comments

Christian Czaia [Decadis AG]

Maybe those custom fields are bound to the issue types through a context? If not they should show...

Jobin Kuruvilla [Adaptavist]

For simple search, no. Advanced searching doesn't have that restriction!

Magnus Haglund1

Well.. when I configure which columns are shown in the issue navigator (advanced searching) there is shown this note:

Not all the fields below are shown in the issue Navigator for each issue (eg custom fields which are only per-project and/or per-issue type)

We are using Jira v5.1.3

Magnus Haglund1

Nope, no context are used for the custom fields.

Magnus Haglund1

And yes, I am using advanced search and it does restrict showing custom fields when the result includes several different issue types where the custom fields are only used by some of the included issue types.

Jobin Kuruvilla [Adaptavist]

Oh sorry, if you are talking about result columns, then yes. It is restricted in both cases. I thought you were talking about the fields displayed while searching.

There is no workaround to avoid it. Actyually, it is designed to work that way because it doesn't make sense to show fileds which doesn't belong in the context of the query.