Hi Everyone,

Thank you for taking the time to provide your feedback. Your insights and suggestions have been instrumental in shaping the way you can interact with attachments on the issue view, and we are truly thankful for your ongoing engagement.

Moving forward when an issue has over 150 attachments, it’ll only display attachments in the list view.

You’ll be able to:

• View attachments in the list view.
• Upload an attachment.
• Download a single attachment.
• Download all attachments on the issue at once.
• Delete attachments.

The new experience has commenced rolling out, all users should receive the experience within 3 weeks.
If you want to want to better work with over 150 attachments per issue, you can look for other file storage solutions on the Atlassian Marketplace.
Read the announcement here

Thank you again for providing your valuable feedback on this issue. I'll close this issue. 
Ahmud
Product manager | Jira Cloud

Hi all,

My name is Venkatesh and I’m a product manager on the Jira cloud team. Thank you for leaving feedback on this ticket. Given the level of interest in this ticket we’ve researched and assessed supporting more than 120 attachments in the new issue view.

Decision

Based off our research, we won’t be supporting more than 120 attachments for now

Reasoning

We assessed different use-cases for having more than 120 attachments and decided to keep this limit because

• Having more than 120 attachments contributes to slower performance, larger amount of bugs and decreases the usability of Jira. Our team’s focus is primarily on making Jira easier and efficient to use, and supporting this feature detracts from this goal.

• Upgrading our service to support more than 120 attachments poses a security risk for our customers. At Atlassian, security is one of our companies highest priorities for our customers and we wouldn’t want to jeopardise our customers' security.

Next Steps

I am going to convert this to a feature request so that we can continue to gather feedback. I know this won’t be the decision a number of you are looking for, and I’m sorry for that. We believe this is the best decision for most users, with the information we have right now.

If you would like to connect to talk about why you require more than 120 attachments, please feel free to email me at vvasudevan@atlassian.com so we can discuss your use-case in more detail.

We’re always looking to reassess and improve our experiences. If new information comes to light that suggests we should iterate this approach, we’ll definitely reconsider. Please remember that jira.atlassian.com is one of many inputs for the Jira roadmap. You can learn more about our process here.

Thanks again for your feedback.

Venkatesh,
Product Manager,
Jira Cloud

Old Update
This issue was formerly tracked by: https://jira.atlassian.com/browse/JRACLOUD-72355

As part of tracking the previous ticket we rolled out an improvement that doubled the number of attachments an issue could hold prior to failing from 60 to 120. This ticket represents the continuation of this work and the seperate issue of handling more than 120 attachments on an issue.