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
Next: Root
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.
Hi,
How do you or would you manage your tickets/reporting/QA if you are facing the following situation?
Context:
- Epic is used as Potential shippable product (PSP)
- PSP has multiple stories
- Each story has test cases (Zephyr)
- Epic has a general test case (we test the feature, once all stories are complete)
Problematic:
After the story gets Accepted by our Product Owner, it passes to a end-to-end round of testing. One story can be QA done, but would have to wait before deploying it until the Epic is fully tested. When we do search tickets: we can see much more tickets that are QA done, but only a couple can be deployed.
What is your recommendation? Best practice?
Thank you!