Looking to show burndown during a sprint when dev and testing are done but additional work is needed Edited

I would like to start by saying that I understand this isn't a pure agile way to do things but it is the scenario I am faced with and could use some advice. Our 2 week sprints include both development and testing. However,  after the sprints are completed and before the release, we still have a period for integration testing. The dilemma I am struggling with is coming up with a jira workflow that shows burndown during the development/qa sprint (which I believe means we would need to mark the story Done once testing is complete). However, then we would still need to know that there is more work (integration testing) that needs to be done to those same stories before we release. Does anyone else have a similar workflow and could share how you handle this? Or can anyone come up with a workflow solution in JIRA without having to clone every single story?

0 answers

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,795 views 11 18
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot