Getting last comment with lookupissue

[Vikram K]

Hi,

I am trying to generate an email when a sprint is closed with a list containing issue key, status & last comment. 

I am using lookupIssue for this, the other fields are populating fine. But Iam unable get the last comment with {{comments.last.body}}

please let know if I am using the right smart value 

Thanks

[Jehan Bhathena]

Hi @Vikram K 

This works for me:

 {{#lookupIssues}} {{key}} {{comments.last.body}} {{/}}

Adding my automation rule and it's output below: (NOTE: my trigger is a "SCHEDULE")

I even tried the same code block that you've mentioned in one of your previous comments

Gave me this output

[Ste Wright]

Hi @Vikram K 

I tried this and it also didn't work for me, strange!

Can you show us how you are trying to visualise the data once looked up?

Ste

[Vikram K]

@Ste Wright 

I am having a list to show the issues in the Sprint. The key & summary seem to come up right, last comments seems to have the issue

Sprint Summary
<ul>
{{#lookupIssues}}
<li>{{key}} - {{summary}} - {{comments.last.body}}</li>
{{/}}
</ul>

[Ste Wright]

Hi @Vikram K 

That does work for me, both your version and the option @Jehan Bhathena provided above.

And it works in both the comment field, and in email.

Ste

[henry_lin]

Hi @Vikram K 

I tried inserting the script you provided above and I'm still not getting the comments. Is this solution on for cloud? I believe I'm on server

[Bill Sheboy]

Hi @henry_lin -- Welcome to the Atlassian Community!

As this is an older thread, I recommend creating a new question, perhaps including a link back to this one.  That will ensure the maximum number of people see it to offer suggestions.

Back to your question...

If you are asking about accessing Comments from the Lookup Issues action results, that will not work for Jira Data Center.  That version of automation only supports a limited number of issue fields: https://confluence.atlassian.com/automation/jira-smart-values-issues-993924860.html#Jirasmartvaluesissues-lookupissueslookupIssues

There are two possible workarounds, depending upon your rule structure:

• use the bulk-handling feature of the Scheduled Trigger or branches, with the plural {{issues}} smart value
• use the Send Web Request action to call the REST API to perform an issue search with JQL, and access the fields from the web response.

Kind regards,
Bill