Automation failing with weird message

[Tim Foster]

I have an automation rule that's failing and the error doesn't seem to relate to my rule.

The error is:

REQ-209: "((key = ) AND (key != REQ-209)) AND (project in (10016))" - Error in JQL Query: Expecting either a value, list or function but got ')'. You must surround ')' in quotation marks to use it as a value. (line 1, character 9)

Which seems to be a straightforward syntax error. However, I can't see how this relates to my JQL. The branches are meant to pick up for a change on a sub-task, so that the Parent (the task) will transition to the same state as the sub-task, and the Epic (parent of the task) will do the same. The parent aspect works fine, but the parent's, parent (the epic) fails with the error. My JQL is, as you can see form the screenshot "key = {{issue.parent.Epic.Key}}"

What am I doing wrong?

 

[Tim Foster]

I have worked out what the problem here is. It seems that the automation is firing itself and it's on the second execution that it fails. To resolve it, I've unchecked the flag that allows it to be fired by other rules and it's all good now.

[Bill Sheboy]

Hi @Tim Foster 

That error message seems to be coming from another location in the rule than the image you posted.  You can confirm that as the JQL in your branch is much simpler than what the error indicates.

Please post an image of your complete rule, and provide details of other areas in the rule which use JQL to gather issues, such as a schedule trigger, branch, or Lookup Issues action.  Thanks!

Kind regards,
Bill

[Stefan Salzl]

Hi @Tim Foster ,

I can reproduce this behaviour by deleting the epic link in the parent. Are you sure that the task/story (whatever your parent is) is created withn the epic or does have "epic link" and was not linked to the epic by issue linking?

Could you maybe show a screenshot of your issue?

Best
Stefan

[Tim Foster]

REQ-209 is definitely a task within the Epic (REQ-135). I can expand the epic in the roadmap and see the tasks underneath it. 209 has four sub-tasks. I think it is failing when the last sub-task is marked as done, but I've added a log into each branch so I can say for sure which aspect is triggering the failure.

Let me get that first, then hopefully I'll have better info to provide.