To display parent issue custom field on send email automation

[Kelvin Po Keng Siong]

I am unable to get the automation to include custom field information from the parent issue.

Custom Field = custom_10157
Custom Field Data = Andrea

What I expected was,

Corporate IT confirmed that Andrea access has been removed.

What I got was,

Corporate IT confirmed that access has been removed.



Please advise.

Thank you in advanced.

[Bill Sheboy]

Hi @Kelvin Po Keng Siong 

When an automation rule references the other issues linked to the current issue (e.g., the parent) only some of the linked issue's fields are available.  If it did not do that, you could imagine that a single issue could yank in tons of data, though subtasks, issue links, etc.

To assess the other fields, that related issue must be loaded somehow.  For your scenario, I recommend first using the Lookup Issues action with JQL to load the parent issue, and then reference its custom field you show, such as with:

{{lookupIssues.first.customfield_10157}}

Kind regards,
Bill

[Kelvin Po Keng Siong]

I am sorry, I am pretty new with this automation thing. Is it possible to share with me a guide how to load the parent issue with JQL ?

Thanks in advanced.

[Bill Sheboy]

First, successfully using automation rules requires learning and experimentation.  I encourage you to learn more by trying things.  

To help with your rule writing, please refer to these documentation and example sources:

• https://www.atlassian.com/software/jira/guides/automation/overview#what-is-automation
• https://www.atlassian.com/software/jira/automation-template-library#/rule-list?systemLabelId=all&page=1&pageSize=20&sortKey=name&sortOrder=ASC
• https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/
• https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues
• https://support.atlassian.com/jira-software-cloud/docs/use-advanced-search-with-jira-query-language-jql/

For your scenario to get the parent data, try the lookup issues action with JQL, such as:

key = {{issue.parent.key}}

Once that parent is loaded, its fields can be accessed.  How that happens depends upon the type of field you want to access.

It appears your field is a user-picker field.  Thus you need the smart values for a user field type: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-users/

For example, that might be this for your field:

{{lookupIssues.first.customfield_10157.displayName}}

[Gary J]

so whats the proper syntax so that it looks up the parent issue first then look up the custom field (user picker) to mention in the comment?

[Bill Sheboy]

Hi @Gary J 

That may be done using the Lookup Issues action with JQL, as described in my post above.

Kind regards,
Bill