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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

how to increase the max attached file size larger than 2GB

According to the guide I can set the max size of attached file.

And the configuration permits the size less than 2GB.

but because of  my issue mgmt. we need to handle files that is more than 2GBytes.

Is there possible way to resolve the my need?

1 answer

1 accepted

0 votes
Answer accepted

I would strongly recommend that you do not try this.

Jira is not a file store system, it can, and will, fail randomly if you try to upload or download large files.  Rather than try to use it as a file store, I would look for another system to store huge files.

Ok ! Thank you Nic.

Then if the users in issue tracker need to attach some huge files such like logs or test binary on a issue. How can we support the user's needs.

They want to upload/download huge files rapidly for their job.

I think that we need co-works with a huge file transfer method(agent), file storage system and JIRA issue.

I want to use the JIRA as a Issue tracker with huge files.

Can you advise a strategy or idea to resolve my worry about handling huge?

thanks in advance.

Attaching huge files to an issue tracker is rarely the right thing to do.  Look at why they want to attach things and fix that.

You've given us two examples of why people are attaching things, and both of them need fixing:

  • Logs: Why are your logs more than a few liines that say where the error is?
  • Test binary: This should never be done.   if something goes wrong in a binary then people should be naming the version they are using that they got from your build servers, or if they built it themselves, the version of the source code.

If you insist on "attaching" large files which no-one will ever find useful, then you should build a large file store service and ask people to use that, putting urls pointing to the file into the links fields on Jira issues

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

7,138 views 8 28
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you