Changing the Size of the Fix Versions and Affects Versions Select List
This page describes how to increase the size of the Fix Version/s and Affects Version/s drop-down lists. Please see Changing the Size of the Fix Versions and Affects Versions Select List for the full feature request.
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.
From <jira-install>/atlassian-jira/WEB-INF/classes/velocity.properties:
- 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.
This workaround will apply to all Fix Version/s and Affects Version/s drop-down lists in the instance.
Increasing the size of the field
Edit <atlassian-jira/WEB-INF/classes/templates/jira/issue/field/components-edit.vm. Change the line:
<select multiple name="$field.id" size="#minSelectSize ($versions 1 6)" id="$field.id">
For example, if you wanted to make it 15 (in the case where there are more than 3):
<select multiple name="$field.id" size="#minSelectSize ($versions 1 15)" id="$field.id">
Make sure to back up the velocity file before changing it. Keep in mind the notes from Modifying JIRA Templates and JSPs.