Attachment health check shows warning message when a custom attachment page is used in Jira Server and Data Center
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
On Jira Health Check page, there is a warning message:
Custom attachment paths are deprecated and won't be supported since Jira 10. To change the location of attachments, create a symbolic link for the current attachment directory.
Cause
The admins use a custom attachment page although they link the default folder to the custom one with a symbolic link. As mentioned in the warning message, the custom attachment paths are deprecated and won't be supported since Jira 10.
For Jira Data Center installations with a single node, where a $JIRA_SHARED_HOME folder is defined, users need to make sure that $JIRA_SHARED_HOME/data/attachments is set as the attachment path, which is the default for these environments. Having the attachment path set to $JIRA_LOCAL_HOME/data/attachments, even if there's only a single node, will throw this warning.
Resolution
If you still the warning even though you link the default attachment page to the custom folder, follow the steps below and change the settings in UI:
- Navigate to Administration > System.
- Select Advanced > Attachments to open the Attachment page, which states whether attachments are on or off.
- Click the Edit Settings button, which opens the Edit Attachment Settings dialog box:
- In the Attachment Path field, choose the Use Default Directory option.
- Click the Update button to update Jira's attachment settings.