Updating an issue takes too long - Jira DC.

Question

Hi everyone,

we have recently (last two months) upgraded from Jira server to DC.

Right now, when updating an epic (and only an epic), it takes like 18 - 20 seconds to complete the update or creation.

Epic has some automations as script listeners, behaviors, scripted fields and WF scripts.,

but when disabling all scripts related to the epic it does not change the actual update / create run time.

I also created a new project based on the 'problematic' project's configuration.

When mapped all scripts to the new projects, it took something like 7 - 8 seconds to update, same scripts, same mapping, same configuration.

I tried looking in the server logs and read over the internet to solve it, but no luck.

Any one has ever got into this?

Thanks.

Shachar Ovadia_6glu7h · Answer

Well, actually it is so much faster when i execute an update or create.

Now I am trying to refactor some of the code related to epics actions.,

Some of the code contain for loop and nested loop like matrixes and so, so it kind of 'complex' i guess for the Jira host machine to process those calls.

What would you suggest for the next steps ?

Thanks.

Nic Brough -Adaptavist- · Answer

Scripts don't run or compile in the script editor, they run when they are triggered by the actions you have configured them for.

What happens if you create Epics in projects with no scripted actions or fields set up?

Shachar Ovadia_6glu7h · Answer

Hi,

Thank you so much for your reply,

Our all scripts is saved in the Script Editor, and listeners and scripted fields compile the script via the script editor,

Is it possible this is also a cause of a delay ?