@Chris Gillis

Yes but you have to do it every single time (you could save a link to avoid it, but not when you embed the roadmap in a Confluence page), and it doesn't work when a task is still not set as Done even if the Epic is.

You can filter the roadmap list to not include Done items.

https://imgur.com/2pGJ5vl

Can you please do this one ASAP – this makes our roadmap unreadable.

How is this not done already? This thread in the community is one of many I found when looking for solutions: https://community.atlassian.com/t5/Jira-Software-questions/When-an-epic-is-complete-on-a-Next-Gen-project-how-do-you-remove/qaq-p/1021371

These requests have been around for years at this point, and would be something the entire user base would benefit from. 

Also our team could really do with this feature.

Erika – if we can't hide Epics, can we archive Epics as part of the option to do so?

Unless hide/archive seems to functioning the same way.

Please advise.

This would be very helpful! Currently I'm deleting epics after they get done but it's not sustainable...

Knowing Atlassian: they will only add this feature to their very expensive premium roadmap feature set...
Forcing you to upgrade all of your users to the expensive premium plan, even tough only 1 or 2 users in your company will use the roadmap...

Really expect this feature!

Hi everyone, 

This is Erika, PM for the roadmap team. Firstly I'd like to apologise to everyone for the delay with this work. We’re acutely aware that this is a really annoying problem for the roadmap customers today. Please know this is on our radar, but we can't comment on an exact time when it will be available. If you have any more feedbacks or suggestions, please feel free to reach out to me at esa@atlassian.com. 

Cheers,

Erika Sa

Atlassian Product Manager

I'd add that I'd like this to carry over when the roadmap is linked into a Confluence page. I figure if there's an auto archive tool, what is embedded in the Confluence page would only include the same info as what is presented in Jira, however when I try @alexleonov's suggestion above (ie. using the full link to the pre-filtered roadmap) I still get a preview in my confluence page that shows all of the old done epics. So I thought it worth mentioning. 

Using the filter field to select all statuses but "done" does not work for me as it also filters the stories within an epic and I want to see them all when expanding a large feature.

I too am looking for a date when this will be ready. It is an issue in our Jira Cloud Next Gen Roadmap

Thanks!

Hi,
Any idea when this will be ready?
We have this issue with our Jira Cloud Next Gen Roadmap.

I am seeing the same issue as Irena Lam. Filtering out Done Epics is only possible when all child tasks are also marked as done.

I've discovered this kind of by accident: when already in the roadmap view, you can filter by statuses (just below the word "Roadmap"), and then you can bookmark the URL so that the filter is 'on by default' - not very elegant, but does the job until the feature arrives.

When we do quarterly planning it would be really helpful if we could turn off the done epics. Or have a way of keeping filters always on by default.

It's really odd to me that even if the Epic is marked DONE, if there's even one task inside that's TO DO or IN PROGRESS the whole epic will still show in my roadmap view. I want to keep those tickets open (since I can't resolve anything for other reasons besides done besides just deleting which isn't ideal) but i don't want my roadmap view to get all clogged up. 

Would love if this gets prioritized since it's been 6 months and so many people are asking for this. 

Also, 14 days is odd...as a user I just want it to be hidden when I need it to be hidden, not a random number of days later. 

Agreeing with everyone here, a way to archive epics on the roadmap feels essential for any long term projects. Hope to see some progress on this, thanks for the hard work Jira folks!

Piling on here: the inability to filter epics makes this feature unusable. It shouldn't be some arbitrary time limit before things disappear (I'm referring to the 14-day concept proposed as a solution which makes no sense). Instead, I want to simply be able to filter I can clearly see the Epics related to a specific focus. The Status filter is unsatisfying because it currently filters Stories, not Epics, so if an Epic has any Story with that status, the Epic still shows up.

Just enable filtering on Tags.

Just here to +1 this issue. This is a glaring oversight in the Roadmap feature that will make this frustrating to use in a matter of months. Concerned to see this "in progress" for so long as our team shifts to using a next-gen project.

Agree.  Without the feature, roadmap is inevitably going veerrrrry lengthy that way as time goes by.

I've been using Jira less than a month and am finding that this is an absolute must. Only googling for a solution lead me to this issue. This was created on 03/Jun/2019 and one still hasn't been made available? All we want is the ability to filter out epics based on whether they are done or not, I would think this to be an easy implementation.

Wondering what the progress is on this.  I too have a use case for being able to selectively show Epics in the Roadmap.  A manager would like to track some but not all the Epics (only the highest level ones) and I can't do that since all Epics show up.  Just some simple way to filter the Epics that get shown on the roadmap is very needed.

I agree with Fowler, this needs to be fast-tracked as it's a simple filtering option/change.  Or at least allow the user to configure the roadmap view so that we can make the edits to the view ourselves

This issue has been "IN PROGRESS" since 29/Aug/2019 12:51 AM. What in the world is going on?

if we could have a simple toggle in each Epic to choose whether or not we want them to be shown in the roadmap, it could be great

Or an ability to set a filter query for the roadmap, which will achieve the same thing - then everyone's different needs might be addressed by them changing the query.

Or show label toggle like boards view, it enables me to set epic label "wip" and I can show the wip label only.

Sorry, this cannot help, it needs to label all epics, issues to show.

Understand you need to prioritise so I will just add myself to the upvoters for this feature.

Hi f80b53ecd246 f77f06d07c2c both are great ideas! I've shared your thoughts with my designer and they will be properly explored when this work is prioritised and back on track (in a few months). Thank you so much for sharing!

> Hello @ErikaSa, if we could have a simple toggle in each Epic to choose whether or not we want them to be shown in the roadmap, it could be great

Or an ability to set a filter query for the roadmap, which will achieve the same thing - then everyone's different needs might be addressed by them changing the query.

Hello @ErikaSa, if we could have a simple toggle in each Epic to choose whether or not we want them to be shown in the roadmap, it could be great

Hi everyone,

My deepest apologies for the delay in update. Unfortunately, this work is currently de-prioritised for the team to complete another project. We're hoping to get back on track around April but given its high demand, we are discussing a short term interim solution. I will come back with more updates on this soon.

In the meantime, please feel find some time with me here. I'd love to chat about your needs and whether the solutions we've explored will meet them. 

Cheers,

Erika Sa

Atlassian Product Manager

so - any news about this?

how can I upvote or help promote this issue?

Suggestion: 

• Automatically hiding epics doesn't seem to be a full-fix as some Epics might be idle because of blocking issues or a simple holiday. For example: we have clients who are inactive during the Christmass holidays, which is 2 weeks. 

• I would like to be able to manually 'hide' any epic and reveal hidden epics as I would do with a filter. 

This is fascinating. I think I may have made a terrible mistake by picking next-gen Jira - our roadmap looks like a passive-aggressive joke now that we've got half a year of completed projects before anything current shows up. But at least file uploads work now!

Hello? What's the status of this?

Any updates? How long it will take? 

I would prefer we have control over if they are archived or not.  We shouldn't need to wait for 14 days to go by.  We should be able to bring them out of archived status as well.  I believe adding the additional status of Archived is the only thing needed. Done would still be visible (to status in meetings, etc), Archived wouldn't.  

I don't see this as just hiding "done" issues. Sometimes we have Epics that go on Hold and we don't want to work on them at this time but don't want to close them out either. It would be nice to have those not show as well. I like the idea of being able to set what the default view is based on the statuses you want. So for us we would want to see "in progress" and "to do". But we don't want to see "done" and "on hold". Like everyone else has said we want the ability to see all the different statuses if we want.

+1 this is a really annoying feature to filter out 'Done' epics.

I suppose some settings for roadmap view needed. Where you can set status filter by default.

+1 for @michaelasp proposed solution. It's a pain to use the Roadmap view and always needing to hide the Done epics to be able to see something properly.

Ben, will it be that they are removed when done, after 14 days or will the filter default be To Do and In Progress?.  WIll the list of filter options change if we add statuses or will they be the standard To do and In Progress and Done classifications

My preferred fix for this would just be to set the default view to filter out "Done" epics (so it only shows "To do" and "In progress" epics. This seems like the quickest and simplest change that doesn't break or add to the UI in any way.

While it does distinguish between done and epics in progress/to do, if they stay there forever we would have an encyclopedia of epics - hard to focus on the ones that matter at the time. 

@pkqk Also curious to know does the archiving filter after JQL features when referencing Jira tickets in confluence ?

Also on top of being able to set the filtering for the roadmap macro would be good to also allow filtering based on labels, so i can for example have a roadmap macro that shows me everything in progress with a certain label.

This helps for reporting purposes to the business.

I am with @pkqk , @Carlos Pereira @Ben Jackson, this is not about marking it as done or differentiate it with on progress / todo. 

The point that @pkqk mention is definitely also my difficulties, the part that I cant use confluence macro properly is one of my main concern, since there is no way I would have the macro reflect very large table that doesnt necessarily reflect the current status of projects (i.e. it is a very large table that displays unuseful information (the done epics).

The other thing is also, it is also painful to keep on dragging newly created epic to the top, since it is buried down below because of those done epics.

We migrated our project to the next gen board, and the roadmap page is not very useful.

• You have to manually sort the Done epics to the bottom
• The filter selection isn't remembered
• The filter can't be linked to from the confluence embed

Having them hide after 14 days like issues on the board would be a huge improvement and consistent behaviour.

Not per se 14 days of inactivity, why's that part of the user story? Done is done. These are not issues, they're epics.

Thank you Ben. That is useful.

carlos.pereira the roadmap does visually distinguish between regular and done epics - They have the tick and turn grey.

Hi everyone, thanks for the feedback. I am a PM at Atlassian and we are looking at this work right now. I'll keep you updated as we progress this.

Just in case there's a relationship, I filed this issue yesterday as well  https://jira.atlassian.com/browse/JSWCLOUD-17997  Epics marked as "Done" are returning a status indicating they are not done when using the Jira REST API.