Currently JIRA provides a 'Sub-Task Blocking Condition' workflow condition. When including this you must select all statuses that sub-tasks may be in for the transition to proceed. The basic assumption of this implementation is that a blocking condition will primarily exist during 'Closed' type transitions, and sub-tasks must first be closed.

I'm requesting an improvement to allow the sub-task blocking condition to apply only to sub-tasks of a particular issue type.

The following is our use case:

We have subtasks "Customer Build", "Finance Order", "IT Process", "Support Query", etc
Each of subtasks uses a workflow including the following statuses: "New", "Open", "In Progress", "Ready for QA", "Closed"

We want our parent issue only to transition if all 'Customer Build' subtasks have been closed, regardless of the state of other subtasks. With the current implementaiton this is not possible.

One possible workaround is to have the 'Customer Build' subtask use entirely unique statuses. This would allow the condition to, for example, require a 'Customer Build Closed' status as well as every possible status of non Customer Build workflows. This is less then ideal and having more complex criteria for this condition would be useful.