I had a search and couldn't find this anywhere, apologies if it is a duplicate.
I'm wondering if it is possible to setup Greenhopper so that it prohibits users from transitioning a Story through the work flow if the story has unresolved Tasks/Bugs linked to it.
An example would be that you have Story 1, and linked to Story 1 is Task 1, Task 2 and Bug 1. If any of these linked issues are not in the Closed state (or another state if we so chose) I'd like it to be impossible to transition Story 1 through the workflow.
The thinking here is that it will make sure that we're not launching a story that isn't complete or has outstanding issues associated with it. For instance, if there was a bug we weren't going to fix, we'd have to suspend it etc
I think that's done by making the Tasks and Bugs be sub-tasks of the Story, and then using the Blocking workflows by subtask status instructions:
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...
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