our team has a DEV board and a QA board. when we close a sprint in the DEV board, we want to push the issues into the QA board (tasks that are in the QA Release column)
We are using JIRA On-Demand version
The way we currently doing it is the following:
We have a DEV Scrumboard with these columns:
Our QA board is actually a Kanban board because in our case QA is working for different teams and issues might be tested during the DEV sprint as well as after the DEV sprint. Once the story/bug/improvement reaches our "custom" status "To Be Tested" it is displayed on the QA board because the QA filter defines that.
Since the To Be Tested status is in the last column of our DEV sprint those issues are "removed" from the DEV scrumboard once we end the sprint.
So basically the filters behind your boards manage this in combination with the fact that the status which is linked to QA is in the last column of your Scrumboard.
We do the same as Maarten. The filter is the same in both boards. The difference is that you map different statuses on each board.
Ex. you have statuses (Open, Progress, Closed, QA Progress, QA Closed)
In one board you map (i.e. assign status to column) like this:
Open, Progress, Closed (leaving the QA statuses unmapped)
The other board maps like this:
Closed, QA Progress, QA Closed (using Closed as the starting point on this board)
I hope this clears it up for you.
We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...
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