Atlassian does not support customisations to Velocity templates or other JIRA files. For more information about Atlassian support, see Atlassian Support Offerings.
Deploying Velocity Templates without a Restart
In a development instance, you can play with picking up velocity file changes without a restart.
- Change class.resource.loader.cache from true to false
- Uncomment (remove the # sign from) #velocimacro.library.autoreload=true
Keep in mind that the next time you upgrade JIRA – or need a new installation for any reason – you will have to manually copy any changes you have made to the JSPs or tempates into the new installation of JIRA. If the JSPs or templates have changed in the newer version, you will have to port your customization into them.
Some times it is nice to display the header row when viewing a list of sub-tasks in the Issue Detail view. There was a post about this in our forum community: http://forums.atlassian.com/thread.jspa?threadID=27500.
In order to accomplish this, it is necessary to modify
<install directory>/atlassian-jira/includes/panels/issue/view_subtaskissues.jsp. Then implement the following method. setDisplayHeader as follows:
Restart JIRA for the change to take effect.
this is not applicable for JIRA version 4.4 and above as the view_subtaskissues.jsp file no longer exist