Our Jira has been crashing pretty often of late with no discernable reasoning, and we are wondering if its just system overload (memory + processor) due to the highly complex workflows we have running all over the place.
We arent a big company (about 100 jira users, obout 80% of whom use Jira daily) and have our set up in compliance with the recommended settings.
However, one of our most-used wokkflows has 24 steps with various post-functions, conditions and I think a validator or two in between. Just seems like a lot of thinking for jira to do at once across multiple tickets...
Wondering if anyone can speak to this from experience
I don't think, that the problem is caused by the length of your workflow. We have 92 different workflows, some of them with 12 steps, but mostly all of them with conditions and functions.
Have you already tried to increase memory? Is there something in the logfiles before your Jira stops working?
Do you have any external plugins / apps installed? If you have any apps that you don't need necessarily, disable them.
We had some years ago a problem, with one of our applications updating an issue field with lots of data by the REST api. It added more and more text to the field, again and again and after a while, Jira crashed because of this.
Maybe you also have such a client application?
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs