toLowerCase() on loop value not working

Owain.Esau

Hi,

Im trying to create an automation rule that looks at the subject or description of emails for key terms that are defined as an asset. The automation rule should then update the work item and update the queue field and assign then assign a user to the ticket. This is all working but only when the subject field in the asset is all lower case.

What i wanted to do was this:

"type": "jira.comparator.condition",
    "value": {
        "first": "{{issue.summary.toLowerCase()}}",
        "second": "{{businessrule.Subject.toLowerCase()}}",
        "operator": "CONTAINS"
    },

Where businessrule is the name of the loop value, but when using toLowerCase on the loop value it clears it so tries to match against "" and always passes. What I've ended up having to do is enter the subject in the asset to be all lower case and remove the toLowerCase() function call on the second value shown above.

Is there any way around this? In its current state if anyone were to add a new asset object with an uppercase letter it would always pass and result in every ticket going to the same queue.

Bill Sheboy

Hi @Owain.Esau -- Welcome to the Atlassian Community!

As @Marc -Devoteam- describes, we need to see your automation rule and audit log details to provide more context for the question.  Including, what type of branch are you using?

 

Until we see those...

If the rule branches over object / asset data, it is possible there is a timing problem looking up the value fast enough before the toLowerCase call.  The solution for that would be adding an extra step to fully evaluate the asset value, storing it in a variable first:

• branch: over the objects, with a branch variable named businessrule
  • action: create variable
    • name: varSubject
    • value: {{businessrule.Subject}}
  • smart value condition:
    • first value: {{issue.summary.toLowerCase()}}
    • condition: contains
    • second value: {{varSubject.toLowerCase()}}
  • todo

You may also want to confirm the case is correct for Subject, versus subject as the attribute the rule sees.  This could be done by writing the value to the audit log inside the branch.

 

Kind regards,
Bill