Jira automation fails when adding DONE AND CANCELLED

[Bill Ewald]

I have an existing automation rule that will set the Story to DONE when all the Sub-Tasks are set to Done (When all sub-tasks are done → move parent to done).  Works perfect.  We now have administrators using the Cancelled status in their Sub-Tasks, so I need to adjust the automation rule.  

When: Issue is transitioned to Done

For Parent - Status does not equal Done.  And: Sub-tasks match "status = done". Related issues = Sub-tasks.  Condition = All match specified JQL.

Then: Transition the issue to Done.  

When I change And: Sub-tasks match "status = done OR status = cancelled" or "status = done AND status = cancelled" the rule fails to transition if the sub-tasks are set to cancelled.  If one sub-task is set to cancelled and one sub-task is set to done the rule fires appropriately.  I have tried many possible variations in changing\adjusting the "And:Sub-tasks match" field.  

Is there something specific to the Cancelled status?

Thank you for your help.

[JP _AC Bielefeld Leader_]

Hi Jim,

you redirect every request to https, but you didn't setup any vhost for port 443 (https)...

Best

JP

[elmer25]

JP, Thank you and you are correct on the redirecting to https inside the Apache conf. The redirection is to the AWS Load Balancer which is listening on port 443. From the load balancer, the target is back on port 80. There is no redirect to 443 from the load balancer. As such all requests from the Load Balancer to the target is on port 80.