Lookup with destinationissue is failing

[Rafet Karaoglu]

Recently, one of our critical automations has stopped working. 

We have the custom issue link types "Requirement" and "Test" in our instance. We have dedicated issues for our requirements, development tasks and test cases. They exist in separate projects. We link our requirements and test cases as part of our planning.

When a development task is described, we link it to the requirement issues. At this point, our automation used to link relevant test cases to the development task. We had the following rules in the automation:

Normally, when the development task is linked to the requirement, the issue is triggered. Then the lookup linkedIssues({{destinationIssue}}, "is tested by" finds all test cases attached to the requirement. In the final step, test cases are linked to the development task. Until Jan 11, 2022 everything was working fine. However, now the audit log shows that the 2nd step with the lookup issues returns no issues. Is {{destinationIssue}} smart value no longer supported?

[Rafet Karaoglu · Accepted solution]

Thank you for the responses, this was working fine until recently but it seems that a change took place.

This automation was a project specific automation (because we don't want it to trigger in different projects on our instance). However, with a recent change {{lookupIssues}} query can only return tickets in the same project so no issues were found and linked. 

Since then, I updated the scope of the automation to cover the project which contains our test case issues. Now the lookup can detect them properly and in the final step, they are linked to the issue that triggered the change.

[Bill Sheboy]

Well done!

[John Funk]

Hi Rafet - Welcome to the Atlassian Community!

I have not used lookupIssues in that way, but why can't you just use a Branch with Linked Issues?

[Bill Sheboy]

Hi @Rafet Karaoglu -- Welcome to the Atlassian Community!

First thing, I agree with John's suggestion to use a branch with the JQL in your Lookup Issues instead of the lookup.  The lookup probably doesn't help for this use case.

And...I am surprised that the Link Issues action works (worked?) with {{lookupIssues}} as the results previously contained several fields other than {{key}}.  Since around the end of November 2021, it now contains all of the issue fields.

If you look at your audit log from when you believe the rule was working and compare to now, what do you see: one issue, multiple issues, nor no issues being linked?  Were there any errors?

Perhaps if you post some images of the audit log that would help provide some context for what is happening.  Thanks!

Kind regards,
Bill