How can I expand a rule?

[Phil Bustin]

I'm simplifying this question:

I have a rule to transition a parent issue when all the sub-tasks are completed.  It works with one sub-task/Issue Type/workflow: {{issue.issueType.name}} equals "Dev Task".

I created a second sub-task Issue Type, but when I tried to add it to the compare using {{issue.issueType.name}} equals "Dev Task" "Software Move Issue Type", the automation log shows: "The following issues did not match the condition:" and the sub-task issue key.

Is it possible to use Compare to include multiple Issue Types?

My original Details for this post:

I have a rule (below) that works for a sub-task workflow.  I added a separate sub-task workflow, because for one issue type, I need a screen, but not for other issue types.

Sub-task A always is always automatically created from a particular parent transition.  Sub-task B can be created from the same transition at the same time, zero to 7 times, depending on checkboxes in the parent transition.  That automation is already working.   

I know I can use one sub-task workflow instead of two, by having in the one workflow two transitions instead of one; have a different screen for each transition with appropriate fields displayed for each; and hiding one transition or the other using transition condition(s), but I don't know how I would hide fields in the two workflow statuses for one kind of issue.

My second question is, with the two sub-task workflows, how would I expand my rule so that it requires that all sub-tasks are complete before triggering the transition in the parent?

I believe the Trigger and the second Compare will work, because the two workflows share common statuses.  The Trigger should confine the rule to the desired sub-tasks and not others, because no other sub-tasks in the project contain these statuses.  

I changed the first Compare to {{issue.issueType}} and Sub-task, but it apparently isn't working.  Since there are two issue types, if I go back to {{issue.issueType.name, I don't know whether or how the rule can be changed so that it looks at both.

Then I changed the Compare to {{issue.issueType.name}} and "Dev Task" "Software Move Issue Type", but got the same result.

1) Original rule that worked when there was one sub-task issue type (one workflow):

2) New rule :

3) New rule log, showing success only because of comment written to log:

Note that the same Advanced compare condition that did not work appears for both sub-tasks, that use different Issue Types and workflows but share the same statuses.  I also get the same result if I don't use quotes around 'Sub-task'.

If there is a solution involving a branch and/or if/else, I keep losing the ability to find if/else.  I'll keep looking, and if I find it again, I'll try to record the hidden path.

3) Log for rule with {{issue.issueType.name}} and both issue type names:

[Phil Bustin · Accepted solution]

I got the automation to work by removing the first Compare.