This page last changed on Aug 30, 2010 by jcostello.

Customisations to Velocity templates or other JIRA files are not included in the scope of Atlassian Support.
Deploying Velocity Templates without a Restart

In a development instance, you can play with picking up velocity file changes without a restart.
From <jira-install>/atlassian-jira/WEB-INF/classes/velocity.properties:

  1. Change class.resource.loader.cache from true to false
  2. 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.

The default Free Text Custom Field editor renders as a textarea that is 4 lines long. This may be too small for comfortable data entry and editing. The functionality that controls the behavior of that field is hardcoded in file <install directory>>atlassian-jira/WEB-INF/classes/templates/plugins/fields/edit/edit-textarea.vm. Edit all occurrences of parameter rows in the edit-textarea.vm file to the desired value and restart JIRA for the changes to take effect.

RELATED PAGES
Page: Removing Commas for Values Held in Number Field Custom Field Type
Page: Changing the Size and Content of the Components Select List
Page: Removing NONE from the Issue Security Drop-Down List
Page: Changing the Size of the Fix Versions and Affects Versions Select List
Page: How to Remove 'NONE' from a Select List Custom Field
Page: Changing the Size of the Text Area Custom Field
Document generated by Confluence on Mar 27, 2011 18:50