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.
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.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.