Currently, on a GreenHopper Kanban board, I have a filter which deliberately filters out parent issues of a certain type (e.g., "Test Case") yet allows the sub-tasks (e.g., "Test Instance") of that type. Test Cases have a completely different workflow from Test Instances, by design.
I'm aware that, within JIRA workflows, it is possible to force the transition of a parent issue when all sub-tasks have transitioned to the same status, but I do not have anything like that established.
What's happening: when I transition a Test Instance sub-task to the "Passed" column on the board, I have to "Acknowledge" that the parent Test Case cannot be transitioned to the same column since it does not have a corresponding transition in its workflow.
Question: how can I tell GreenHopper not to try and transition the parent issue when the sub-tasks are all in the same column/status? I don't want it to do this, and it's annoying that I have to click the Acknowledge button every time I pass a test instance.
Any help is appreciated, thanks!
The only solution I've found is the following:
The status or statuses associated with the parent issues must be in the column that the GreenHopper board recognizes as the "Done" column. So, for my example, I had to move the "Active" status associated with my Test Case issue type to the Done column, and then it stopped asking for my acknowledgment.
Unfortunately, this solution feels a bit clunky because now I have to manage my test cases on the right side of the board while the related Test Instance issues live on the left side.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot