Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Attachment Compression in Jira

We currently have Jira 5.1.3 installed and are upgrading to 6.1.2 for Jira, we have noticed that attachments are automatically compressed in 5.1.3, but cannot find the setting in 6.1.2 that will allow for that same compression.

This presents the issue that when we bring over all our attachments and restore them from the 5.1.3 instance to the 6.1.2 instance, the attachments are compressed and the new instance is not working to uncompress them (or compress new attachments).

I am sure it is a simple setting we are missing in regards to compressing attachments, but we have been unsuccessful in finding documentation online or the setting in the Administration tabs. Could someone point me at the documentation regarding this or list out possible Add-Ons that might peform this task?

2 answers

0 votes

You can try to move manually attachments just coping and pasting them in the new location after the upgrade. You need to restart JIRA after doing that.

Hope this helps,


What does it mean can you please explain, I need to knew more about this topic. now i am awaitng for your kind information, Thanks

Has noone else run across this problem? I would expect that there is a thrid party tool in place here, and surprised its not a default option within Jira to help conserve space.

Suggest an answer

Log in or Sign up to answer