Change Issue Navigator configuration - how to?

Hi All,

we have upgraded our Jira to 5.2.8 couple of weeks ago.

The problem is when you click on the Issues -> Search for Issues then you will be navigated to the Navigator. That's correct. The problem is that by default we get all issues we have permissions. E.g. as a jira-admin I see all the issues in our instance. Because of this the navigator uses to load very slowly.

In the previous Jira version (5.1.2) when we navigated to the navigator we had always the last search result.

Is it possible to change this?

Thank in advance,

2 answers

1 accepted

0 votes
Accepted answer


Rumceisz even though is closed as 'Won't Fix' there is a specific reason for that, as it makes it the behaviour of Issue Navigator consistent.

In our tests, for example in our support system with 400K issues and our public facing instance with around 200K issues, the navigator loads in a couple of seconds (~3 seconds on an average).

Do you see a different behaviour in your instance?

And I am hoping that JIRA is running as per the recommendations -

0 votes
Mirek Community Champion Jul 04, 2013

Hi Rumceisz,

I am not aware about any easy method (form UI) to change this behavior. The idea behind this is that every search is now treated a separate action. In the old search is was remembering the last search, but this was confusing when you wanted to have two or more searchers. Refreshing Issue Navigator even you have different search was giving you the last search. Now you can have more results.

You only see one set of search results at any given time, even if you have multiple browser windows open. Your search results remain constant until you choose to refresh them. This provides you with a constant set of search results that you can work from when triaging issues. Since your search results don't change as you are making changes to the list, you maintain the original list you started with.

However I agree that when having a lot of issue this could create problems with the performance.

I think that the best solution should be to choose the default filter that you want to start with every new search. That could fix the potential problem.

Best Regards,


Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,946 views 19 22
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you