Documentation for JIRA 5.0. Documentation for other versions of JIRA is available too.

There are some instances where the 'NONE' in the Issue Security Drop-Down list must be removed. By default in JIRA you cannot do this from the web interface. See JRA-5332 for a discussion on this feature request.

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.

This workaround will apply to all Security drop-down lists in the instance.

To remove the field, edit <atlassian-jira/WEB-INF/classes/templates/jira/issue/field/securitylevel-edit.vm. Delete the lines:

    <option value="$!noneLevelId"
        #if ($noneLevelId && $security && $security == $noneLevelId )selected#end
        >$i18n.getText('common.words.none')</option>

Make sure to back up the velocity file before changing it. Keep in mind the notes from Modifying JIRA Templates and JSPs​.

RELATED PAGES
ラベル別コンテンツ

指定したラベルを持つコンテンツはありません。



See our Getting Help page for details.



Raise an issue for our developers.



See answers from the community.



Tweet, blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.