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!
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
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.
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.
You're missing the point - you are going to need to keep restarting your Jira, regularly and frequently.
If you've changed the properties file and restarted, then I don't understand why it wouldn't work - it does here on Test, although I needed to do it twice, and that was after I realised I'd put the wrong owner on the file (must stop doing "sudo bash")
check the docs:
Deploying Velocity templates without restarting JIRA
In a development instance, you can play with picking up velocity file changes without a restart.
- Remove the comment sign (
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.
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...
Teams break work down in order to help simplify complex tasks. This is often done iteratively, with tasks being broken down into smaller tasks and so on until the work is accurately captured in well-...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events