Adding Custom Fields to Batched email gets harder... and harder...

[Adria Alonso]

Hello Community,

I'm a little annoyed about the way now we have to include custom fields in batched emails.

We used to edit the issueupdate.vm and issuecreated.vm with adding the customfield.vm calling the custom fields we needed.

Now this has changed, and following this article, https://confluence.atlassian.com/adminjiraserver/customizing-email-content-batched-notifications-976770772.html

We followed this article and added 

#set ($customfield = $customFieldManager.getCustomFieldObject("customfield_10005"))
#if($issue.getCustomFieldValue($customfield))
<tr>        
    <th>#text($customfield.name):</th>
    <td class="has-icon">
    $textutils.htmlEncode($issue.getCustomFieldValue($customfield), false)        </td>    
</tr>    
#end

Then upload the jar, batched emails stop working...

any suggestions?¿

Thanks in advance

[Adria Alonso · Accepted solution]

Tricky, and cerainly more harder but works:

https://confluence.atlassian.com/adminjiraserver/adding-custom-fields-to-emails-batched-notifications-968669988.html

[Boris Berenberg - Atlas Authority]

Not sure about tweaking the underlying VM templates for batch notifications. But if you prefer to build out a standard set of digests that are configured at the admin level, we support this type of use case in Notification Assistant for Jira (web/marketplace.