Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

{{#lookupIssues}} seems to not give child issues

kfj October 25, 2021

The simplest example I have is as follows:

When: A change in the due date field

Then: Edit issue field (Description)

Issues:
{{#lookupIssues}}
* {{key}}
{{/}}

The result is simply: (and I can empty the filed in advance, so I know it is updating, success in the Audit log) 

Issues:

{{lookupIssues.size}} gives nothing, not even the number 0. It is like there is not even a list. My taret issue is an Epic in a Team managed board, running on a cloud solution. When viewing the epic I see 3 issues listed under "Child issues"

Anyone have any advice?

1 answer

1 accepted

2 votes
Answer accepted
Dirk Ronsmans
Community Champion
October 25, 2021

Hey @kfj ,

In your automation are yo actually filling the list of the lookup? Just calling the lookup smart value doesn't contain anything. You will need to fill it first with a Lookup Action.

 

image.png

You have to add this action before you use the smart value (with a proper JQL), otherwise it will just be an emtpy smartvalue.

https://support.atlassian.com/jira-software-cloud/docs/automation-actions/#Automationactions-Lookupissues

kfj October 25, 2021

Thank you! That was the missing piece from the example I read.

Just a followup question. In my real automation I have a Branch rule, which gives me the epic (this works). Are there any direct access to the "Child issues" from the epic, or do I need to use this Lookup issue action?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events