nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Attachment files suddenly became unavailable. What's causing this?

Daisuke Niwa

Hi there,

One of our customers is using very old version of JIRA.

They reported that suddenly attachment files (to JIRA issues) became unavilable from issue screen.

What is causing this problem? If anyone has a clue, please let us know.

Regards,

Daisuke Niwa

Accepted answers

parthiban subra1

Not much has changed in the way attachments are stored and configured in JIRA.

I can only think of these reasons

Attachments are switched off or JIRA does not have permissions to the filesystem where this is stored.

Check those conditions and see if something has gone wrong there.

If this is not a system wide issue and at project level check the project permissions.

All comments

Norman Abramovitz

Which Jira version is having this issue?

parthiban subra1

Not much has changed in the way attachments are stored and configured in JIRA.

I can only think of these reasons

Attachments are switched off or JIRA does not have permissions to the filesystem where this is stored.

Check those conditions and see if something has gone wrong there.

If this is not a system wide issue and at project level check the project permissions.

Daisuke Niwa

Thank you for your comment. The thing is, only some of attachments are unavailable. Others are fine. Can a permission issue cause such problem?

Daisuke Niwa

It's 3.11.

I know it's EOLed long time ago but this customer is unable to upgrade JIRA quickly.

parthiban subra1

You can control, who can delete and create but as long as you are able to view the issues you should be able to see the attachments.

are they able to see these issues?

Nic Brough -Adaptavist-

Yes - check the Operating System permissions on the files (and, of course, the directories they are in). If the ownership or permissions on those have been changed, it could be that the changes have meant the user running Jira can't read them any more (by "user running Jira", I mean the user account the service is running as, not the humans logging into it)