That usually happens when you've got the right data in the database, but the attachment file is physically missing from the the file system, or unreadable by the user Jira is running as.
Check the file system ownership of the attachments directory, and if the file is there (you'll probably need to look in the attachments table to work out what the file path is)
I've seen it happen many time when you migrate Jira and upgrade in a single step. If the attachments are not yet in the $JIRAHOME/data/ folder at the time Jira starts to do the upgrade, then the filenames are not getting altered as per the upgrade, but the database tables that reference the filenames could be changed.
If that happens, I'd recommend reverting the upgrade, OR perform the upgrade again on a test server and this time make sure the attachments/avatars are in the correct position on the filesystem before starting up the upgraded version the first time.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.