...
Warning |
---|
|
Please acknowledge the following before installing JFS: - JFS patch should be properly applied to your JIRA Jira instance; patching is mandatory; patches are distributed as separate ZIP files at the Downloads
- You must restart your JIRA Jira immediately in case of any change made to JFS state via UPM (aka 'Manage Add-onsapps'). This includes installing, enabling, disabling, upgrading, uninstalling etc. of JFS add-onaddon.
- You also must restart JIRA immediately if you update UPM add-onaddon. Updating UPM causes reloading (i.e. disabling then enabling) of all user-installed pluginsapps, including JFS, which in turn requires JIRA restart.
|
...
Tip |
---|
title | To check if the JFS patch is applied properly: |
---|
|
- After JIRA has been started, navigate to
Administration -> System Info ; Modified Files section should look like this:JIRA 4.0.2-4.2.4: Panel |
---|
| [Installation Type: Standalone] secure/views/issue/moveissue-confirm.jsp, jira-application.properties, secure/views/issue/convertissuetosubtask-confirm.jsp, com/atlassian/jira/issue/history/ChangeLogUtils.class, entitydefs/entitymodel.xml, templates/plugins/issueviews/single-word.vm, com/atlassian/jira/issue/history/ChangeItemBean.class, templates/plugins/jira/issuetabpanels/changehistory.vm, com/atlassian/jira/plugin/atlassian-bundled-plugins.zip, com/atlassian/jira/issue/fields/CustomFieldImpl.class |
JIRA 4.3-6.4 (JFS patch v1.2): Panel |
---|
| [Installation Type: Standalone] secure/views/issue/moveissue-confirm.jsp, jira-application.properties, secure/views/issue/convertissuetosubtask-confirm.jsp, com/atlassian/jira/issue/history/ChangeLogUtils.class, entitydefs/entitymodel.xml, atlassian-bundled-plugins.zip, templates/plugins/issueviews/single-word.vm, templates/plugins/jira/issuetabpanels/changehistory.vm, WEB-INF/lib/jira-api-4.3.1.jar, com/atlassian/jira/issue/fields/CustomFieldImpl.class |
JIRA 7.0 and later (JFS patch v1.3.0): Panel |
---|
| [Installation Type: Standalone] lib/jira-api-7.9.2.jar, entitydefs/entitymodel.xml, templates/plugins/issueviews/single-word.vm, com/atlassian/jira/issue/history/ChangeLogUtils.class, com/atlassian/jira/issue/fields/ImmutableCustomField.class, secure/views/issue/moveissue-confirm.jsp, jira-application.properties, secure/views/issue/convertissuetosubtask-confirm.jsp, templates/plugins/jira/issuetabpanels/changehistory.vm |
If it looks like the one below - the patch has not been applied properly: Panel |
---|
| [Installation Type: Standalone] jira-application.properties, entityengine.xml, secure/admin/user/views/userbrowser.js |
|
Info |
---|
title | Attention International Users |
---|
|
If you are using non-English language and your default operating system encoding is not UTF-8 , it is strongly recommended to set Java default encoding to UTF-8 . To do this: set Java property file.encoding
to UTF8: -Dfile.encoding=UTF8
.
You can find more info on how to set Java property for Tomcat installed as a Windows Service here: http://confluence.atlassian.com/display/JIRA/Setting+Properties+and+Options+on+Startup#SettingPropertiesandOptionsonStartup-TomcatinstalledasaWindowsService%3A
License is needed for the plugin to operate. To get an evaluation license:
...