Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

General JIRA Usage with large attachments

Deleted user Nov 04, 2016

Hi everyone

This is not a specific question, but I'm hoping to get some input as to how my small department is using JIRA.

A year ago, we started using JIRA and we were very happy with the many options and how fast we could adapt it to our needs. We have a server hosted at a company near us and everything has been working great.

This summer, it was decided to try and use JIRA, not only as our workflow, but also as a database for the many files we use in our production. Files, which often are around 1gB.

Being a bit worried, by this sudden influx of large files (1gB-file to around 1000 issues and rising) I asked our hosting company, if they saw any problems with this approach. They did not.

Fast forward to now, our JIRA instance is running very poorly. Originally, we had simply run out of disk space, but after increasing that this week, we are still facing performance issues. For more info, we have around 30.000 issues in total, 100 custom fields and around 1000-2000 issues with large attachments and rising.

I asked our hosting company, to look into increasing the performance on the server our JIRA instance is running from, but they charge a significant price for this.

My question is then:

Do you consider our use of JIRA, as production database, as a good idea?

It is reasonable to continue down this road and upgrading our server?

Will the server upgrade even fix the problems of bad performance, or is there underlying architecture in JIRA, that makes it bad at handling this way of using it?

If this question is not meant for this board, I am sorry.

/Nikolaj

1 answer

1 accepted

2 votes
Answer accepted

For the last years i scrutinized every such request.

JIRA is a ticket system, not a fileserver and every tweak made (if only to increase attachment sizes from 10mb to 11mb) this will have an exponential effect, make stuff like backups, migrations, mirroring to test environments and upgrades a living hell. You are much better of adding a custom field that points to a network/samba/cifs/ftp/scp/git-repo path than actually including it all in the attachment directory.

Just my 5 cents, other people might not agree.

Deleted user Nov 04, 2016

Hi Jonas

Thanks for your input. I will definitely look into your suggestion! This will also make it easier for me to make a case for my superiors smile

Our hosting company didn't agree, but I fear they were not the most impartial source, since whatever added cost we have, directly improves their bottom line....

/Nikolaj

 

I'm with Jonas on this - JIRA is not a file storage system.  If you have large files, a proper file store and linking is definitely the way to do it.

Deleted user Nov 06, 2016

Ok, thanks for your input Nic smile

I'll look into a solution like "network/samba/cifs/ftp/scp/git-repo".

Deleted user Nov 07, 2016

A followup question: Doesn't JIRA Confluence "solve" our problems? Or is it maybe too extensive, just for file storage.

Conflluence is not a file storage system either.  It's good if you import the data and convert it to proper pages, but uploading large binaries is the same for Confluence as JIRA.

Deleted user Nov 07, 2016

Ok, thanks again Nic!

I'm very grateful for your help smile

We have customers using 500MB attachments in JIRA and Confluence, so it works. But we don't recommend it due to maintenance headaches. Options such as Box are better for this

Hi,

Are there any available plugins to integrate a storage service within Jira so that the experience for end user is straightforward and files can be uploaded and linked in the ticket interface

Inside Jira - no, because you'll have exactly the same problems with it that you do with the current one.  It's not the code lacking file-handling here, its the architecture of the server making it hard or impossible.

But if you want to integrate with external file stores (i.e. Jira running as one service, file store as another), then yes, there are quite a few - MattS already mentioned Box, but there are several apps for linking Jira into file stores.

Best thing to do is select a list of good file stores that works for you (ignoring Jira for now), and then look through the marketplace to see if there is a connector app for it for Jira.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June ask me anything (AMA)

Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...

146 views 9 10
Read article

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