JIRA automation is not working properly

[SHANAVASH MOHAMED]

Hi Team,

I created the JIRA automation for condition based.

1. If condition will be working fine

2. Else if condition is not working .

i have attached the screenshot for your reference find the screenshot. please do the needful for ASAP, 

Thanks 

SHANAVASH M

[Support Team [Clearvision]]

Hi SHANAVASH 

I believe the issue here is if you have an issue with an empty component list it is not going to hit the if or else statement

It will be filtered out at the component not in Discovery or Eng. Improvement Feature steps

https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-operators/#Advancedsearching-operatorsreference-NOT_IN

The "NOT IN" operator will not match a field that has no value (i.e. a field that is empty). For example, assignee not in (jack,jill) will only match issues that have an assignee and the assignee is not "jack" or "jill". To find issues that are assigned to someone other than "jack" or "jill" or are unassigned, you would need to type: assignee not in (jack,jill) or assignee is empty.

Whereas if an issue has the component Product & Service development then it will match the component not in Discovery or Eng. Improvement Feature as it has a component and it is not either of the two specified. It will therefore get to the IF statement and execute the create task action

[Support Team [Clearvision]]

FYI here is a test rule I created

[SHANAVASH MOHAMED]

Thanks @Support Team [Clearvision] 

Thanks for quick response, But i tired this condition also still issue is not creating.

find the screenshot for your reference, please do the needful.

Thanks 

[Support Team [Clearvision]]

Could you provide a full screen shot of the rule?

[SHANAVASH MOHAMED]

Hi @Support Team [Clearvision] 

Please find the screenshot for your reference.

Thanks

SHANAVASH M 

[SHANAVASH MOHAMED]

[Support Team [Clearvision]]

Hi 

You still have the same issue due to the reason we mentioned previously

The "NOT IN" operator will not match a field that has no value

So your first and second issue match JQL conditions will only match if there is a value in the component field. If this is empty it will not continue.

Try using the example rule from the screenshot in our previous comment