How to make changes to JSP files always reflected after the service restart

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

When working on customization tasks, it is sometimes beneficial to directly update JSP pages in Jira with a custom content. However, upon modifying the respective JSP template, the changes may not be reflected in Jira even after the service has been restarted.

Environment

Any Jira DC installation where JSP customization is needed. 

Solution

Visit Precompiling JSP pages for details on how to do this.

Updated on February 25, 2025

Still need help?

The Atlassian Community is here for you.