Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 21:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×I have a custom field named 'Release Month' of type Paragraph (supports rich text) in every ticket. I want to send the list of tickets in a fix version via email to a set of users. This list should include the above custom field.
I used Jira automation and managed to trigger the email, but the custom field is not displayed. The standard 'Issue' fields are displayed.
The content section of the email looks like this:
Look up issues starts here
{{#lookupIssues}}
* {{key}} - {{summary}} - {{issue.customfield_1234}} - {{issue.Release Month}} {{/}}
Look up issues ends here
As you can see, I tried the different variations I read on the internet to fetch the custom field. 1234 is the customfieldID of Release Month. The email displays the standard fields Key and Summary. Also the intended bullet points show up as asterisk(*)
The output I am expecting is an email with a bulleted list of tickets and their release month. If this works, I might consider converting the list to a table.
Any help will be highly appreciated.
Hi Erfan,
Without looking into your rule in too much detail straight away, what I notice is that you've used the 'issue.' part in the referring smart values. You've done this for the custom field, but not for the key and summary. And there lies the answer: When you're using LookupIssues, it already assumes you're looking 'in the issue', hence you don't want to add the 'issue.' part in the smart values.
So, it will likely work like this:
* {{key}} - {{summary}} - {{customfield_1234}} - {{Release Month}} {{/}}
Thank you. That worked :-) Is their any way to get the bullet point to work too?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey,
I would say your approach should work - @Bill Sheboy as our lookupissues/automation guru, could you maybe shine some light here?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Erfan Afthab and @Hans Polder _Devoteam_
The answer depends upon the field type and markdown used. For example, if your email format is HTML, try that syntax for list items.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for the responses. I got it to work. My code and settings added below from everyone's benefit.
Created a variable named IssuesReleaseMonth: <ol> {{#lookupIssues}} <li>{{customfield_1234}}</li> {{/}} </ol>
And selected HTML in 'Send as' drop-down of the 'Send email' settings.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.