Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
6.4.9
-
6.04
-
17
-
1
-
Description
Migrating/upgrading JIRA from one server to another may cause conflicting attachment paths between the jira.path.attachments from the application propertyentry table and the default attachment file path.
This can cause confusion especially if the JIRA instance is moved between two different operating systems.
For example:
___ Application Properties _________________ jira.path.attachments : E:\Program Files (x86)\Atlassian\Application Data\JIRA\data\attachments
___ File Paths _____________________________ JIRA Home : /opt/app/JIRA/Data Location of atlassian-jira.log : /opt/app/JIRA/Data/log/atlassian-jira.log Index Path : /opt/app/JIRA/Data/caches/indexes Attachment Path : /opt/app/JIRA/Data/data/attachments
It is understood that this "jira.path.attachment" property is not used once the new default "Attachment Path" gets used from that point in. We would recommend possibly removing this old entry entirely from the database once the change to default occurs as to not confuse customers when looking through the logs.
The "jira.path.attachment" property is not used once the new default "Attachment Path" is used. This information in the System Information and jira log files can be ignored.