Time to SLA app utilizes all possible ways Jira API offers to minimize load on your Jira instance and under normal circumstances it works without a heavy impact on performance. However some of our customers observe contrariwise situations mostly caused by external effects such as overall high load on Jira instances, complex app integrations or in some cases internal effects such as high number of SLAs. One significant drawback customers face is relatively slower issue loading times after issue transitions.
This problem is caused by SLA calculations happening during issue transitions.
Asynchronous update is recommended as the solution to this problem. Since SLA updates will be executed asynchronously after the issue events, issue load times are significantly lower, however, in exchange changes on SLAs will be reflected with a delay which is nearly one minute.