Jira Automation detecting Issue Type of Sub-task not matching

[Ilya Sadukovskiy]

I am trying to add automation that has a step in detection if issue type is Sub-task, however it does not match as expected. Help appreciated. 

Below you will find screenshots of automation workflow and it goes into Else block instead of IF. Also attached are screenshots of Issue Types. Additionally I must add this rule is global.

[Bill Sheboy]

Hi @Ilya Sadukovskiy -- Welcome to the Atlassian Community!

Would you please post an image of the audit log details showing the rule execution, for more context?

That appears to be a team-managed project, rather than a company managed one.  (You may confirm that by looking for the project type at the bottom-left side of the page expanding area.)

Team-managed projects each have their own types, and so the exact type may not be the one you are checking in the condition.  Please try writing this to the audit log before the condition to check the type:

type name: {{issue.issuetype.name}} and id: {{issue.issuetype.id}}

Kind regards,
Bill

[Ilya Sadukovskiy]

@Bill Sheboy  Sorry for delayed response.
It is a team managed project.
Here is what was logged:  `type name: Sub-task and id: 10035`

[Bill Sheboy]

Thanks for that information.

Would you please post an image of the audit log details showing the rule execution when the condition does not match?

[Ilya Sadukovskiy]

I tried modifying the IF condition to this. Have not yet confirmed if that will work

[Bill Sheboy]

There is an error indicating an attempt to set the Assignee during the transition to DEV COMPLETE.  What is in that rule action in regards to Assignee?

Next, I was asking to see the audit log for the rule as it was written before, and it appears you have changed to try to check by issue type's id.  Please retest after that change and then post the new audit log details image.  Thanks!

[Ilya Sadukovskiy]

The log attached is before my changes. I applied changes just now. The original question has the if condition I have been originally using.
The Assignee error is separate issue, but it it very strange one. I just picked to Assign user to Unassigned and it complains. 

[Bill Sheboy]

Please re-test your rule after the changes which look specifically for the issue type id in the condition.