Automation filtering lookupissues by summary & type help

Question

This seems like it should be simple, but I am banging my head against it all morning.

I just want to make an automation that looks up tickets that meet 2 criteria.

1. Have a certain keyword in their summary ("Q4" in this case)
 2. Are TASKS (and not sub-tasks, stories, or epics.

Currently I have that step trying:

{{lookupIssues.summary ~ Q4 AND lookupIssues.issuetype.name = Task}}

Currently this returns some things with "Q4" in the summary, omits others, and includes epics and sub-tasks. Overall it seems like its finding some data, but nowhere near the correct data limited to those qualifiers. Help appreciated, thanks!

Bill Sheboy · Answer

Hi @Mike Siciliano -- Welcome to the Atlassian Community!

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas. Thanks!

Until we see those...

I am unfamiliar with the syntax you are showing, and wonder how it could work at all.

Do you want to gather the issues with the Lookup Issues action and filter later or filter before loading them?

To filter later, please try smart value, list filtering with some text and list functions:

* https://community.atlassian.com/t5/Automation-articles/Filtering-smart-value-lists/ba-p/1827588
* https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#indexOf-String-str-
* https://support.atlassian.com/cloud-automation/docs/jira-smart-values-conditional-logic/#equals

For example:

{{#lookupIssues}}
  {{#if(and(summary.indexOf("Q4").gt(-1), equals(issuetype.name,"Task")))}}
    * {{key}} -- {{summary}}
  {{/}}
{{/}}

To filter before loading, you could adjust the JQL used for the action.

Kind regards,
Bill