As you can see from our doc Get started with next-gen projects
In a next-gen board, if an issue sits in the Done column for more than 14 days, it automatically gets archived. You can view all archived issues by selecting the Looking for an older issue? button.
If your project is new, you won't be able to see this button for now, you'll need to wait a few days and then those issues will, automatically, be archived.
Let me know if this helps!
Same dealio yo. Might the crickets speak up?
Also interested to know if others are keen to be able to sort the Epic order in the board as well (hint: I am). If so please upvote the item below.
Hi @Ben Jackson ,
Thanks for picking this up.
I'm antisocial media so can't tweet you. Simple 2-minute fix is to just set the roadmap as filtered by default to only show active epics.
Then the user can choose to see historical epics by setting the filter to all epics.
I have a question for everyone here. If done epics are removed from the roadmap do you have a need to see them again at some point?
See them again from where? The Roadmap? (Regardless of what the precise context is, I'm sure someone somewhere will need to see them again.)
I would be happy if the filters of "todo", "in progress", and "done" would persist across browser sessions, similar to how the "Views" filters persist (see attached image).
Same as @AL FOR, I also bookmarked the page with the filter preset to "to do" and "in progress".
Not having filter persistent is definitely not ideal, it makes content less discover-able by the rest of the team (aka nobody will looks at them).
Furthermore, this issue extends to the new the Confluence Roadmap Macro.
Very nice feature to share content with people outside Jira.
However this time there is no way to save the filter (even if you paste the link with the filter preset)
So the confluence macro ends up looking like this:
Very informative page...
@Ben Jackson I bumped in to the same probelm with @Jacques Barbe I am trying to use the confluence roadmap macro, but since there is no way for me to filter the relevant epics, then the macro ended up looks chaotic, especially since I am running a program which consist of multiple project running in parallel, it would be very helpful to be able to implement this, thanks.
Agree with you guys - I've inherited a roadmap with 20 - 30 epics on it, many of which are long since done. The roadmap is a bit too messy to be useful. I don't want to delete old epics as it is useful to keep the documentation somewhere, hence the need to be able to remove or unlink epics from a roadmap.
@Ben JacksonWhile you guys are on it, I think that the best way to go about this is to add a flag or setting for each epic which controls whether or not it shows up on the roadmap.
In my opinion completed Epics are one part of the story that clogs up the roadmap view but we also have Epics which are related to miscellaneous items or bugfixes and more or less document "ongoing" work - I definitely do not want to see those on the roadmap as well. The roadmap view also implies that every epic has a start and due date which again is not the case for all Epics - some are extremely long term and it makes no sense to keep them on a roadmap.
So please, add a simple feature that just shows or hides epics on the roadmap - we can then decide whether we will select done epics or any other combination
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events