Hello community, I have the following problem.
I am creating an automation that allows me to send an email daily with a list of issues based on certain criteria.
The body of the email to be sent must contain the following fields:
- Key
- Summary
- Assignee
- Last comment made
- Date of last comment
So far I've got the first 3 fields working, but I'm needing help identifying the smart values for the "Last comment made" and "Date of last comment" fields.
Email Content:
List of issues:
{{#lookupIssues}}
<li><a href="{{toUrl}}">{{key}} - {{summary}}</a> {{assignee.displayName}}</li>
{{/}}
___________________________________________________________________
Below I attach a screenshot of the automation.
I hope you can help me solve it, thank you very much!
Hi @Dario Alarcón , thanks for your question.
You can send the mail with the following content to include "Last comment made" and "Date of last comment" values.
{{#lookupIssues}}
<li><a href="{{toUrl}}">{{key}} - {{summary}}</a>
{{assignee.displayName}}
{{fields.Last comment made}}
{{fields.Date of last comment}}
</li>
{{/}}
or
{{#lookupIssues}}
<li><a href="{{toUrl}}">{{key}} - {{summary}}</a>
{{assignee.displayName}}
{{fields.customfield_xxxx}}
{{fields.customfield_xxxx}}
</li>
{{/}}
If this helps you, you can accept and vote.
Hi @Murat Seven , thanks for you response.
Because those fields are not custom fields.
What I need to obtain is the last comment that was made on the issue and its respective date.
For example:
If an issue has 5 comments, I only need the content of the last comment and the date that comment was made.
I explain?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah, you can format it like this;
{{#lookupIssues}}
<li> <a href="{{toUrl}}" >{{key}}- {{summary}}</a>
{{assignee.displayName}}
{{comments.last.body}}
{{comments.updated}}
</li>
{{/}}
if the issue is not resolved, you can provide feedback.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Excellent, that helped me a lot!
Is there any possibility that it does not take into account the attachments that are included in the comment? That is, it only shows me the text of the comment made.
Because the email received arrives this way and is unfriendly:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Excellent, this helped me a lot!
Is there a possibility that attachments of the "image" type are not taken into account when inserting the comment?
Since the email arrives in the following way and is quite confusing:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you @Dario Alarcón , I'm glad I could help. You can accept and vote on this request.
and I think it can be done. I'm sending the document. You can review and test it.
for example:
{{#if(not(issue.attachment))}}
{{comments.last.body}}
{{/}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Murat Seven , but i dont understand where i must put these code?
This is my code in the email body:
{{#lookupIssues}}
<li><a href="{{toUrl}}">{{key}} - {{summary}}</a> 👉 {{assignee.displayName}}
💬 {{comments.last.body}}
📆 {{comments.updated.convertToTimeZone("America/Argentina/Buenos_Aires").shortDateTime}}
</li>
{{/}}
For example, I have an issue that has 5 comments and there is one of those comments that has several images attached, what I need is for those images not to be taken into account when displaying the comment, but only to show me the text of the comment.
Is that code you gave me useful to do that?
Where in the code should I place it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Dario Alarcón , I apologize for missing your message.
I see there's an FR ticket that is aiming to address the issue that covers a similar angle.
In the meantime, I recommend upvoting the ticket to follow any future development or product updates.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.