Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Epic filter in the backlog and link to the issue navigator

Hi the community,

I currently surprised by the following behaviour:

- In the backlog view, if i select on the left an epic i will only see the associated stories (which is nice),

- then: issue_navigator.png, Hence i'm expecting that the issue navigator will be opened showing me only the 2 stories out of 47,

- But finally i get in the issue navigator all the story without considering this filtering through epic.

For me it sounds like a bug but some could say it is designed as intended. Any opinion on that.



1 answer

We use JIRA 7.12 server version.


I don't think it is a bug.


The 'View in Issue Navigator' function shows you the entire contents of the Sprint. It does not include any filters you have applied -- before clicking the icon.


The Backlog is a 'special sprint' for all issues where no Sprint is assigned.

This is, in my opinion, a little bit weird since in addition you have on the left a "clear all filters" link. We can then expect that what you will view on the issue navigator is related to the filter. For me this is misleading but i could understand that at the level of Atlassian it could be considered as "designed as intended".

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events