we have an issue with kanban boards. We have tasks which represents more or less complex stores. Some of the columns of the board represent developers activity (ready for dev, dev in progress, ready for qa). As soon as developer starts to work on a story he creates some subtasks, example:
Story: add field xyz to dialog foo
subtasks: write sql script, implement service, implement html dialog...
The subtasks make perfect sense in the development columns, but once the stories are ready for QA the task do not make sense enymore.
So for the after development columns like QA -> Ready for Release -> Released we would like to move the parent tasks (stories) only, and were hoping that the subtasks would move atomatically with the parents.
Any ideas how to achieve that?
when I was facing a quite similar problem some time ago, I went nearly mad looking for a solution and honestly have not found one which matches exact our requirements. But I've introduced a kind of workaround which works for us quite well:
We have a quite less complex workflow for the subtasks let's say open/in progress/close (but different status than the stories!).
So opening up the developer-subtask at a certain status of the user story results in an appearance of the subtask in the same column. Then - while moving through the developing process - both issuetypes can move on in parallel (all depending on matching status between Greenhopper and JIRA), until the column Ready for QA is reached. Dragging a subtask here, will close the subtask and thus magically make him disappear and you've only to take care about the story from that moment on.
I am curious if this workaround might work out for you, even if that does not answer exactly the question how to move user stories and subtasks in parallel.
I was investigating a bit more on this topic and found:
With the paid plugin JJUPIN it seems to be possible to satisfy your requirement.
Have you checked out JIRA Workflow Toolbox? It has post functions that allow you to transition linked issues and sub-tasks through workflow. I've tried it out and it works great - you just have to make sure that the post function is attempting to put the linked issue or sub-task to a status that is currently available from it's current status (so if you need it to move through multiple statuses you'll need one post function for each transition).
There's now a very easy to configure way to transition parents and sub-tasks in sync using Automation for JIRA!
(this example transitions sub-tasks, but you could just as easily change this to transition the parent as a result of a sub-task being transitioned)
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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