Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×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: , 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.
rgds,
Romain
Community moderators have prevented the ability to post new answers.
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".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Apply agile practices
Transform how you manage your work with agile practices, including kanban and scrum frameworks.
Learning Path
Configure agile boards for Jira projects
Learn how to create and configure agile Jira boards so you can plan, prioritize, and estimate upcoming work.
Jira Essentials with Agile Mindset
Suitable for beginners, this live instructor-led full-day course will set up your whole team to understand how to use Jira with an agile methodology.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.