Velocity templates problem

[Rumceisz]

Hi All,

we have a blocking problem with the velocity templates.

Story:

our Jira is configured with 2 URLs: one is an internal which can be accessed only in intranet and one is external which can be accessed via internet.

Till now the email template links showing the external links (...external.com) - the base URL.

We created some days ago the internal templates as well with new events, wortkflows, etc and will be applied to those projects that needed.

Steps we did:

1. When we finished with the tmeplate creating we restarted Jira

2. We changed the velocity.properties file:

class.resource.loader.cache=false
velocimacro.library.autoreload=true

3. Then we started to change the templates (fixing the mispelling, etc.)

The first template (HTML Issue creation.vm internal) loaded perfectly after modification.

Then comes the problem: when we changed the other vm templates (Issue resolved, issue closed, etc.) these did not reloaded!! When we tested them, the original templates came to our mailbox.

We doublechecked the events, workflows, project settings and everything was fine.

Can you please help? We totally lost now...:(

Thanks a lot in advance,

Rumi

[Nic Brough -Adaptavist- · Accepted solution]

Um, changing those two flags really is for development systems, not production. You'll find it causes an active production system to start throwing errors (you will lose email at first, but you'll start seeing error in the UI as the damage spreads. I don't *think* you can damage your data, but you will start getting bug reports from users).

It's also unreliable when used in a system with a moderate load (a development system won't be generating hundreds of emails to hundreds of users, but a production one will). Modifications not being picked up is the first sign that you've hit the point where you run out of resources and need to restart, but you'll also find your performance is starting to drag too as it's reprocessing the templates on every single use (for a heavily used Jira)

You really need to reverse the changes to the flags, get your templates settled and tested in dev/test, apply them to live, and restart it.

[Rumceisz]

Hi Nic,

many thanks for the warning. We changed back the velocity.properties settings.

But what could be behind the system which caused that the newer changes did not occur in the emails? Where can we erase the cache? You mentioned the resources: what resources do you mean exactly?

And +1 question if you don't mind: where can we change the URL of the Summary field in the HTML email templates? We really don't find (see attached screen).

Thanks in advance!

Warm regards,

Rumi