nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

AUTOMATION SMART VALUE LOOKUP CUSTOM FIELD EMAIL DISPLAY ISSUE

Mateusz Janus_emo9ao

Hello Brothers and Sisters,

I found the solution for my task in below article

Automation For Jira - Writing a rule that sends an email with the list of open issues per team in a Roadmap Plan | Automation | Atlassian Support

Generally this automation with lookup and variable works perfectly except the one case.

This is my configuration:

JQL

project=cabr and status="DEPARTMENT HEAD REVIEW."


{{#lookupIssues}}<tr><td><a href="{{url}}">{{key}}</a></td><td><a href="{{url}}">{{summary}}</a></td><td><em>{{issue.customfield_10206.displayName}}</em></td></tr>{{/}}

In my email i need to send a list depends on the ticket STATUS -> it works

Depends on the status i want to show columns with ASSIGNE but for some statuses instead of assignee i wanna display custom field (single user picker) . In my lookup i use below smartvalue

{{issue.customfield_10206.displayName}}

THE PROBLEM. At the end email is sent with correct structured lists of tickets BUT my custom field values are not displayed in the email body...I tired differente syntax i.e

customfield_10206

customField_10206

issue.customfield_10206

etc but it doesnt fix my problem

Accepted answers

Bill Sheboy

Hi @Mateusz Janus

Without seeing the details of all your rule actions, I see at least two problems with the rule you show:

First, when using a long-format iterator such as {{#lookupIssues}} ... {{/}} inside of that, the issue prefix is not used as the scope is the lookup itself.

Next, for Jira Data Center / Server automation rules, the Lookup Issues action only supports a limited number of fields, and none of those are custom fields. Here is the open JAC backlog suggestion to add the other fields: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877

The possible workarounds to access the other fields depends upon a rule's structure:

Use a scheduled trigger / branch with the bulk handling feature, using the plural {{issues}} rather than the {{lookupIssues}} smart value. This may not work for your scenario.
Use the Send Web Request action to perform an issue search with JQL, getting the data from the response smart value. This will work for your case, and a single call could be used with all the data, and then filter by the Status value for each case needed.

Kind regards,
Bill

All comments

Mateusz Janus_emo9ao

@Marc -Devoteam- hey my old friend. Any hints....regarding this?

Marc -Devoteam-

HI @Mateusz Janus

Use {{issue.<name of the field>.displayName}}, add a log action to see if this provides the correct name

Example, so if your field is named User, use {{issue.User.displayName}}

Mateusz Janus_emo9ao

@Marc -Devoteam-

hi thanks for quick reply

{{#lookupIssues}}<tr><td><a href="{{url}}">{{key}}</a></td><td><a href="{{url}}">{{summary}}</a></td><td><em>{{issue.Department Head.displayName}}</em></td></tr>{{/}}

My custom field is named "Department Head". Two words....not sure if its issue.

I added log action. But looks like all good... But still in the email values are not retreived

action log.jpg

Marc -Devoteam-

HI @Mateusz Janus

Do the accounts in your DC have a dIsplayName set?

I have tested this on my instance and I have a field manager and on using {{issue.Manager.displayName}}

I get the name set in attribute Display Name, what do you get on using API call:
https://<base_url>/rest/api/2/user?username=YOUR-USER-NAME

Mateusz Janus_emo9ao

@Marc -Devoteam-

let me share just the last line of the log cause of sensitive data

avatarId=11802"},"displayName":"Mateusz Janus","active":true,"deleted":false,"timeZone":"Asia/Riyadh","locale":"en_US","groups":{"size":50,"items":[]},"applicationRoles":{"size":1,"items":[]},"expand":"groups,applicationRoles"}

Is it possible that the problem is because of "Department Head" field name is 2-words field name?

Bill Sheboy

Hi @Mateusz Janus

Without seeing the details of all your rule actions, I see at least two problems with the rule you show:

First, when using a long-format iterator such as {{#lookupIssues}} ... {{/}} inside of that, the issue prefix is not used as the scope is the lookup itself.

The possible workarounds to access the other fields depends upon a rule's structure:

Use a scheduled trigger / branch with the bulk handling feature, using the plural {{issues}} rather than the {{lookupIssues}} smart value. This may not work for your scenario.
Use the Send Web Request action to perform an issue search with JQL, getting the data from the response smart value. This will work for your case, and a single call could be used with all the data, and then filter by the Status value for each case needed.