Custom email template problem

Hi,

in my custom email template i have this snippet

$customFieldManager.getCustomFieldObject("customfield_10609").getValue($issue).fullName

it should return the full name of user in Customfield. However, in the email delivered i dont see the name, but this snippet instead.

In the jira log there is this error reported

notificationType=Current_Assignee,eventTypeId=10070,templateId=28] WARN ServiceRunner Mail Queue Service [velocity] org.apache.velocity.runtime.exception.ReferenceException: reference : template = getEncodedBodyFromContent [line 5,column 12] : $customFieldManager.getCustomFieldObject("customfield_10609").getValue($issue).fullName is not a valid reference.

The funny thing about this problem is, that the very same template runs well on our test envirnoment, which is exact copy of our production enviroment, with the exception that the production one runs on x64 java.

Thanks for any advice and help

Rad

3 answers

1 accepted

0 votes
Accepted answer

what did actualy help was to change the template in following way

$issue.getCustomFieldValue("customfield_10609").displayName

Thanks Teck En from Atlassian support!

 

My guess is that your custom Field ID's are different, which would explain the result.

i have checked the id several times, unfortunately this is not the reason

What is the type of your custom field? if you drop '.fullName' off the velocity reference you should get left with a type [object@13478e] or similar, if that works, it indicates that the custom field does not have the field you are expecting, perhaps a version/api change in the related plugin. If it does not work, it means the issue referred does not have the cusotm field in its context, probably.

0 votes

Does the field has a value in the production environment? On the issue for which the mail is sent?

Hello Jobin,

yes the customfield has a value.

Rad

Suggest an answer

Log in or Sign up to answer
Community showcase
Published yesterday in Statuspage

194 years of downtime: looking back on incident data from 2018

Statuspage customers logged more than 194 years of collective incidents in 2018. That’s a whopping 87% increase from the  104 years logged in 2017 , and we aren’t even through December yet....

45 views 1 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you