Documentation article - Customizing email content in Jira Server

Issue Summary

There were changes to the functionalities revolving around the Velocity Cache. Upon discussion with the development team, we uncovered that the team was not able to control velocity cache invalidation manually, so they changed its flushing interval to something around 5 minutes.

This operation did not have a significant performance impact but allowed users to go back to the default templates without restarting Jira (and make changes to the same templates without restarting the application as well, as a side-effect).

The team mentioned that the part of our documentation that mentions risk should be altered, provided that the articles refer to the versions where the features were altered.

In this case, we are referring to the following message, located at the end of the Optional: Deploying Velocity templates without restarting Jira section:

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.

Steps to Reproduce

1. Access the Customizing email content in Jira Server article.

Expected Results

• Not applicable.

Actual Results

• Not applicable.

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available