You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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.
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.