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

How to filter my Jira Roadmap for all Epics IN PROGRESS and all of their issues including DONE?


I am using the standard version of Jira Roadmap and I wonder if I am missing something here. It seems the status category filters all of the Jira stories and the Jira epics, but I only want to filter on the Epics that are IN PROGRESS and still see ALL of the Jira stories for those epics, including those that are DONE. I don't want to see those Epics that are TO DO.  When I use the View Settings, I can filter out completed Epics. It seems the only way to get around this is to add another label. For example, I could add the quarter (Q2) - which is what our IN PROGRESS Epics are to be - but then I am going to risk missing issues that might not have that label added. That is a terrible workaround in my opinion and it seems like this should be possible within Jira standard version. 

1 answer

0 votes
Trudy Claspill Community Leader Dec 22, 2022

Hello @Nicki Davis 

I know your post is several months old, but I wanted to alert you that it sounds like your issue might be solvable with the roll out of Quick Filter/Custom Filters in Jan. 2023, described in this change request:

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events