Jira automation: Adding lookup issues Epic names to an email

[Nava Bar-Sagi]

Hi,
I am trying to create a report and send via email.
I do not see any way to add the Epic Link (or Name) and the affected versions.
I tried.using:
{{Epic Name}}
{{parent.name}}
{{Epic Link}}
{{customfield_12311140}} as when I expend using "names" I see this field

{{issue. Epic Link}} and the combinations above.
same for versions tried lots of combinations,

For key and summary I used {{key}} and {{summary}} and it worked perfectly.

Thanks,
Nava

[Trudy Claspill]

Hello @Nava Bar-Sagi 

When asking for help with an Automation Rule please provide the following:

1. Screen images showing the entire automation rule.

2. Screen images showing the details of any steps with which you are struggling.

3. Screen images showing the output in the rule audit log.

4. Screen images of the issues involved in the Automation.

With that information we will be better able to provide recommendations.

[Trudy Claspill]

As per the documentation there are only a limited set of fields for an issue that can be accessed through the lookupIssues smart value. Information related to the parent Epic of the issue is not among them.

• {{key}} - Returns the issue key
• {{description}} - Returns the issue description
• {{url}} - Returns the issue URL
• {{summary}} - Returns the issue summary
• {{assignee.displayName}} -  Returns the assignee
• {{reporter.displayName}} -  Returns the reporter
• {{status.name}} - Returns the status
• {{issuetype.name}} - Returns the issue type
• {{resolution.name}} - Returns the resolution
• {{fixVersions.name}} - Returns the fix version
• {{created}} - Returns the date the issue was created
• {{updated}} - Returns the date the issue was updated
• {{project.name}} - Returns the name of the project the issue belongs to
• {{Story Points}}
  • Returns the story points for the issue
  • Since this field is a numerical value, numerical operations such as min, max, average, sum can be executed on the smart value {{lookupIssues.Story Points}}

[Nava Bar-Sagi]

@Trudy Claspill ,

Can you please assist in providing the right syntax?

Thanks,

Nava

[Nava Bar-Sagi]

Thanks, 

What about the affected versions? is it also unavailable?
Is tehre any workaround?

Nava

[Trudy Claspill]

There is no "right syntax".

Per the documentation what you want is not possible.

[Trudy Claspill]

There is an article on the topic of getting data from other fields that are not currently supported.

https://confluence.atlassian.com/jirakb/how-to-use-lookup-issues-to-retrieve-a-single-custom-field-value-in-automation-for-jira-data-center-1455424888.html

The article includes a link to a change request that is still open.

[Nava Bar-Sagi]

Thanks

[Bill Sheboy]

Hi @Nava Bar-Sagi 

Adding to Trudy's suggestions...

Those fields are not available with the Lookup Issues action for Jira Data Center. 

However, if you only want to send an email with the issues, the bulk-handling feature with the plural {{issues}} smart value might help: https://confluence.atlassian.com/automation103/run-a-rule-against-issues-in-bulk-1488594794.html

We would need to see your complete rule image to know if it will work for this approach.

Kind regards,
Bill

[Nava Bar-Sagi]

Thanks @Bill Sheboy 

And again, I was trying so many options that it may be off already, I hope its still clear : )

[Bill Sheboy]

Thanks for that rule image, and it shows you can use the bulk-handling feature:

• Move the JQL from Lookup Issues action to the Scheduled Trigger, ensuring you enable the bulk-handling option and clear the one for "only include issues that have changed..."
• Remove the Lookup Issues action
• In your email action, change {{#lookupIssues}} to {{#issues}}
• test your rule, perhaps running it manually rather than waiting for the schedule

Also in the email action, I notice you have an {{issue. prefix on one of the fields:

{{issue.versions.name}}

Please remove that so the batch of issues is used instead:

{{versions.name}}

[Nava Bar-Sagi]

Thanks @Bill Sheboy and @Trudy Claspill 

I'm in the process of doing that right now.
Looks like better results with retrieving the values.
Somehow the table format is not working now, but I think I can take it from here.

You haves been very helpful with your prompt responses.

[Nava Bar-Sagi]

Hello there, I tried so many options and this is one of them...