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.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
...there's anything I've learnt from working, it's that people are lazy! No offense to anyone reading this, but it's true and we can all admit it. The easier you make something for someone, the more...
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