Our team is composed by a developers team and a testers team.
Since a year now, we were using the Agile SCRUM board to manage our development activity through sprints. A sprint is a two week length time for developers to develop (Fix bugs, develop enhancements/new features). The sprint planning is focused ONLY on development planning.
Now we are aiming to do the same but for Tests planning, we created a new Agile SCRUM board called "Tests management" and a new sprint called "Sprint 1 Testing".
Issues to test are the issues that are "Resolved", "Re-opened" from previous sprints, and can include also some issues that are fixed in the current active sprint which should be tested ASAP like testing showstopper bugs etc.
My question is, can we add an issue to two active sprints? One for the development sprint and one for the testing sprint?
If not, can you please help providing best practices to manage such use case?
I appreciate a lot your help on this important topic!
The main problem of your needs is that you can't have one issue in two different boards, JIRA and GreenHopper will not allow you to have two different statuses and steps for the same issue.
The best approach on my point of view would be to have those two teams sharing the same board using different workflow steps to manage their work. Also you can use sub-tasks for the Testing Team to work on the cases that your Devs have not completed.
In regards to avoid users confusion you can use labels on the issues and/or validators to not allow the users to manage the issue until they are meant to do it.
Create on transition plugin will help you to automate the sub-tasks creation if needed.
I hope it helps!
Hello Atlassian Community! My name is Ada , and I'm the Product Marketing Manager for Confluence Server at Atlassian. If you missed our last post, we're transitioning to quarterly updates&nb...
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!
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