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

Different Issue Navigator Columns per project

Geert Truyen2

Is it possible to distinguish which issue navigator columns need to be show per project?
Depending on the nature of a project, it sometimes very usefull to view different columns.
It would be very usefull to be able to define "views" depending on the nature of the project.

If this is not possible because the columns are universal for all projects, then you need to do this over and over agian when you switch projects.

Thanks for advising.

Accepted answers

Nic Brough -Adaptavist-

Column orders can be saved with filters.

It's not actually useful to try to tie them to projects because a filter can easily include more than one project.

Define filters for your "views" and save the columns with them - that's the best option. With that approach, you can also include more than one project in a view. If a user then comes along and changes the search criteria, or column order, it's fine, because they'll be working on their own copy of the filter and won't affect your defaults.

Also, bear in mind that the issue navigator will drop columns that are not valid based on project and issue type you select. So you can create a filter for say "bugs" which will show all the columns for "bugs", but when used to view "improvements", will drop columns that only belong to "bugs". (This is a source of problems in Jira actually - most of us expect to see the columns with no data, or ideally, a "n/a" flag for the lines a column isn't valid for, and it's a pain that you don't)