Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Forever Epics - Any Alternatives?

Our QA works on multiple projects.  They group their work inside each project into one or multiple epics.  This is a neat way to organize the work and help make it visible to the team and add Epic Links to the cards.  The only issue is that this work never ends.  QA's work never has an end date so we have these "forever epics".  This makes our advanced roadmaps more cluttered and harder to migrate issues if necessary.

Is there an elegant solution to this?

The only thing I can think of is using components to group QA work.

Would love to get some input.


Have a good one.




Hi @Michael McGory 

Would you please clarify what makes these "forever epics" which do not complete and so never close to done?

Even for repeated work, such as test cycles for a feature or regression for a release, that work could be bound to single work items for each need/round.  That would certainly improve reporting and visibility over time.

Best regards,



Maybe not as elegant, but you could have a QA Epic exist for a set amount of time, and then after that time close it and open a new one.


You could have QA not use Epics and have their work be sub-work of existing items somehow.



Log in or Sign up to comment

Community Events

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

Events near you