-
Suggestion
-
Resolution: Unresolved
-
None
-
10
-
Preamble
As of JIRA 8.x, the way the email velocity templates are modified is different from the previous JIRA versions.
Before JIRA 8.x, customers could include an Issue Field by following this article: adding custom-fields to email
As of JIRA 8.x, the method no longer works as the structure of the batched notifications is now different.
A new method exists to add Custom Fields to the Velocity templates, but the method is not suitable for Issue Fields.
The purpose of this feature request is to track customers interest in being able to add Issue Fields to batch notifications and also to document a workaround that customers can implement if adding system field to document is a must in the meantime.
- is spiked by
-
YET-199 You do not have permission to view this issue
[JRASERVER-70206] Adding Issue fields to batch notifications emails
Please implement. Had to deactivate batched notification to maintain previous configurations.
@Zhen Li can you please provide an example for the syntax of using the scripted custom filed in the batch notification email template?
This is a mandatory feature needed before we could consider adopting batched notifications.
Workaround if you have ScriptRunner is to create a scripted custom field for the issue fields. Less flexible and cumbersome, but useable for now.
Is there any update? We just upgraded again and still unable to use system fields!
Completely broke everyone mail filters and we are unable to use the new functionality since they removed this ability.
How hard can this actually be? The batch object has this method
Maybe make it return an object that implements the Issue interface with something other than
throw new UnsupportedOperationException();
for every getXXX() method.