Sub Templates as Reference


I currently have about twenty to thirty email templates set up through JETI. A few of them, between 4 and 10, all use the same HTML table template, but because the wording in the initial text of the email is different for all of them, we have them saved as different template configurations. It's really frustrating, though, when we make a change to this base HTML table, because we have to go into each individual template configuration and change the code to reflect the changes to the base table. Is it possible to create a sub-template, or a fixed set of code that is referenced by JETI email templates, so that when the sub-template is altered in any way, it updates the code on all templates that are referencing it?



Preliminary Test Cases



Tibor Hegyi
June 30, 2016, 5:27 AM

Hi Ethan,

I was thinking of this request and think that the following can be done:

  • there will be a special template type, called something like Abstract Template

  • when you create a new template you can select an existing Abstract Template as its Base Template

  • Abstract template are normal templates, that define the common parts and placeholders (velocity macro calls) for the variants

  • template that are created from a Abstract Template should contain velocity macro methods, rendering the variant parts

If you select a template that has an abstract template as its base, will use the abstract base template's body to render the email, but content from the selected template will be included.

It is just like Object Orientation: an Abstract class with abstract methods and instances that inherit from the abstract parent and implement the abstract methods to make an instance complete.

I think this will be very powerful and will solve your problem. Though it is a different solution to what you proposed because automatically applying changes to exisinting templates is error prone.

Let me know what you think,

Tibor Hegyi
June 30, 2016, 5:29 AM

BTW: we have found a nice WYSIWYG editor that we will incorporate into JETI. With this it will be super easy to change content and look and feel of the templates without dealing with HTML directly.

This will definitely come in August. Furthermore, JETI for JIRA Cloud is on its way to first public release also in this summer.

Ethan Foulkes
July 4, 2016, 6:53 PM

Hi Tibor,

This sounds awesome!

I'm not sure if I'm thinking of it the same way you are...our plan is to have some code (a template) that gets referenced as a part of many other templates which are triggered via post functions. Does this match what you are saying?

Can't wait for wysiwyg =)

January 26, 2017, 1:04 PM

Frankly speaking I do not know if current version has still even plain-text equivalent ... but I would like to ask if so then there could be checkbox try to extract text from HTML one. It is very useful when it is used pretty simple HTML so no table, no images and so ... only like font-size, hypelink, font weight.

January 26, 2017, 1:05 PM

Additionally even custom fields can fix it up ... but I guess that there is issue that it will be seen in email screen amongs fields and this is not so nice.



Tibor Hegyi


Kenneth Breslow



Access to limited visibility issues


Product platform


Module Dependency


Ready for Development


Target version


Fix versions