Why does collecting Change History cause system to not allow updates while running?

[Chris Solgat]

We have a scripted field that loops through the Change History and using a string buffer, displays the entire change history into a single field.  This is being used so the change history can be exported to pdf using the Xporter plugin.  The problem we are running into is when the change history is very long (the script takes over 30 seconds to execute), it seems to lock other users out of viewing and updating issues.  Any idea why this might be happening?  It almost feels like it's putting a lock on the database.

[JamieA]

yes please

[Chris Solgat]

Yes, we certainly can. Should we use the other one that has the code posted?

[JamieA]

Sorry, I meant to post the link: https://answers.atlassian.com/questions/29953319/scriptrunner-script-hanging-up-issue-viewing. Is it the same company? If so please can we work through the one question, because it takes quite a while to get my brain in gear and think about the problem, and it just disperses the information. I thought I had posted on that at the weekend but I looked earlier and didn't see my reply.

[Chris Solgat]

Yes, this is the same issue.

[Chris Solgat]

I'm not sure, but possibly. Where was this question at, do you have a link?

[JamieA]

Does this refer to the same script as Scriptrunner script hanging up Issue Viewing ? It's a very similar question.