nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Activate custom email templates without restart JIRA - How to?

Rumceisz

Hi All,

we created a bunch of new emial templates and we would like to activate them to go on with the work (creating custom events, etc.). In earlier Jira version (major v4) it was possible to change the templates without server restart. We use now v5.2.8 and I'd like to ask you how to activate these email templates without restart?

It is fundamental because our Jira is used 0-24 so a restart is recommended to avoid.

Thanks in advance for help!

Rumi

Accepted answers

Alex Perez

As far as I know, velocimacro.library.autoreload tell Jira to reload and not cache any velocity template. So this may help you if you're changing existing templates that you've already deployed.

But unfortunately, to change this setting you must restart Jira. Also, you must map the events to the velocity templates so it-s necessary to edit the email-template-id-mappings.xml file, and restart jira again.

So ... you-ll need to restart at least 1 time the first time you deploy the templates ... then you can modify these templates without restarting

HTH

All comments

Christian Czaia [Decadis AG]

Hey Rumi,

check the docs:

https://confluence.atlassian.com/display/JIRA/Customising+Email+Content

Deploying Velocity templates without restarting JIRA

In a development instance, you can play with picking up velocity file changes without a restart.
From <jira-install>/atlassian-jira/WEB-INF/classes/velocity.properties:

Change class.resource.loader.cache from true to false

Remove the comment sign (#) from #velocimacro.library.autoreload=true

Making this change in production will eventually lead to JIRA not serving pages along with the ran out of parsers error in the log file.

Cheers

Nic Brough -Adaptavist-

Bother you beat me to it.

I was going to say "you can't do this in 4 or 5 without running out of resources, so you should not really have done it in production in your old version, let alone version 5". Also, you need to restart Jira to pick up the changes in that properties file too...

Alex Perez

As far as I know, velocimacro.library.autoreload tell Jira to reload and not cache any velocity template. So this may help you if you're changing existing templates that you've already deployed.

So ... you-ll need to restart at least 1 time the first time you deploy the templates ... then you can modify these templates without restarting

HTH

Rumceisz

Thanks for the hint!

Rumi

Rumceisz

Thanks for the hint!

Rumi

Nic Brough -Adaptavist-

Just don't forget that you will need to restart your production service regularly, before it chokes up the cache and dies.

You may also experience odd pages going wrong due to this change (with increasing frequency as time goes on between restarts), although they should be fine if the users seeing them simply refresh the page.

Rumceisz

Hi Nic,

actually I need to restart JIRA at least one time for uploading the email setttings to the events. I changed the velocity.properties as detailed above but nothing happened. <br>

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration