Jira Release Note Customisation - What are the risks of enabling velocimacro.library.autoreload

I want to customise the release notes in Jira with my own velocity code. The instructions on the jiradev site say to set the following in a development instance:


Are there any risks in leaving this enabled all the time on our production Jira instance? My confidence in getting the code right first time is low.

Will there be a performance impact on Jira?

1 answer

1 accepted

Accepted Answer
0 votes

Hi Neil,

You'll definitley want to test this in a development environment first, however, there have been some reports in other Communities forums related to issues with leaving this on:

Solved: Velocity templates problem

From the documentation I have reviewed it looks like you only need to use this if you want to make changes to the template without restarting JIRA.  I could be wrong but that was my understanding.  If that is the case I would recommend making the changes in a test/dev environment first and that will allow you to restart JIRA as needed to verify the changes work as expected and then you can make the changes in Production once you're confident the changes work as expected.



Ugh. Thanks Branden. That link has persuaded me to be careful

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 25, 2018 in Jira

Atlassian Research Workshop opportunity on Sep. 28th in Austin, TX

We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...

465 views 7 5
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you