To facilitate deployment tracking: How to track stories' QA done, if epic is not QA done? Edited

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!

0 comments

Comment

Log in or Sign up to comment
Community showcase
Published Thursday in Jira

Updates to jira.atlassian.com give you visibility into what's coming in Jira Server and Data Center

Hello, Community! My name is Gosia and I'm a Product Manager on Jira Server and Data Center here at Atlassian. Since 2002 when we launched our public issue tracker, jira.atlass...

466 views 1 14
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you