Stop Agile Scrum board from Auto-transitioning parent issues

Within the Agile Scrum board, if I transition all the sub tasks to "Completed" or whatever status is in the "Done" column, the Greenhopper board tries to transition the Parent issue to same column.

The issue is that we're trying to use Greenhopper in a way that means that the Sub-Tasks are the specific development tasks that are to be completed. When the Development tasks are completed, it's passed to the QA team (Within the same sprint) for them to test the story. Therefore the Story isn't completed at the same time as all the sub-tasks.

I can't change the way we work, so is there any way to stop Greenhopper from trying to auto-transition the issues?

I've read something that says I should get a prompt asking if I want to auto-transition, however, I don't, I get an error/info message saying that it can't transition the issues as there is no transition.

Is there anyway to maybe configure a dummy workflow transition that makes Greenhopper think it transitioned the issue (when it didn't), may be access permissions etc.

1 answer

I've actually partially solved this by having a second board for the Project Managers to use when closing sprints, but it's not ideal.

Suggest an answer

Log in or Sign up to answer
Community showcase

Scrum Roles Explained: the Do's and the Don'ts

Hello Community,  Today we are going to talk about the three Scrum Roles. There is the Development Team, the Scrum Master and the Product Owner. In my opinion these three are all really impo...

124 views 2 5
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