Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Adding an issue to two active sprints?

Jad HARB
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 10, 2013

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!

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Answer accepted
Thiago Ribeiro
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 10, 2013

Jad,

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!

TAGS
AUG Leaders

Atlassian Community Events