Statusupdates very slow - amount of issues problem?


I'm experiencing problems with status not being updated in a ticket project.
e.g. when answering a customer it takes up to 4 hours until the status is refreshed to "waiting for customer".
I have to mention that this core project is very big with over 180.000 tickets.

Reindex finishes within 20minutes without problems, JIRA itself reacts normally.
16GB RAM, 12 cores, enough free space, DB monitor is okay, no obvious system limitations.

I wonder if the amount of issues is causing this problem (e.g. a cursor iterating over each of the 180.000 tickets checking if there are dependencies) and in general if there's a limit / best practice of how many tickets a project should have in maximum on a Standard JIRA Server.

Any hint is welcome.


5 answers

180 000 is not such a big amount. What DB do you have?

Any third party addons or post functions involved in status update? You may try to disable them.

Only "Email This Issue" but that is imho only involved when creating tickets via email... ?

Try to disable all non-system addons.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 09, 2018 in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

391 views 6 0
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you