we're hosting JIRA on our own servers. Overall, it runs fairly smooth, the performance is OK. But we have one problem: We have a few issues, which were created for logging time the employees spend on general tasks. These issues are a few years old with hundreds of time logs from different employees.
Now the problem is that logging time on these issues feels extremely slow. If you log time while browsing the issue directly, it's just slow. But if you log time from the Tempo Timesheet, it even crashes sometimes.
Is there any way to make these old issues run faster again? Just creating new ones is unfortunately no solution for us (for various reasons).
Regular customer-related issues which normally get closed within a few hours or days run very smooth.
So far, I've created a task, that re-indexes the JIRA databases once a week. Also, I'm re-indexing JIRA itself about once a week. But that doesn't do very much, because overall, JIRA is running smooth.
Thanks in advance,
What is the format of this "time logs" in a JIRA issue?
The only time that we cannot work on an issue is the time when one of our plugins put 15,000 comments on it. We can display the issue but it takes forever. How does yours look like?
Can you generate a HAR dump while opening an issue and display the results here?
I also have the identical problem on any long running issues (the ones we use for general tasks like "general admin"). Tried using the worklog calendar to enter times and also entering a worklog in the issues page. All have the same non-responsive result. The Devs traced it back to a REST call taking a long time (>10s) after you attempt to submit the logged time. Worst, if you add a log entry via the Worklog Calendar it appears to work fast however if you don't wait until the previous entry is completed adding another one overwrites the "uncommitted task". In the "User Timesheet" view the app prevents you moving off the just entered "Log Work" popup page until the commit has happended. Either way you have to wait a long time. Like Gabrielle the workaround of closing and creating a new task for logging the time is not an acceptable option.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot