...
The Asynchronous Update allows you to execute SLA updates asynchronously after issue events. This is an optional function that you can enable if SLA calculations are negatively affecting your transition times.
When does this happen?
If you update the JQL during transitions, we may be caught up due to Jira’s race condition. In this case, the Issue’s index might be finished after Time to SLA starts calculating the SLA. If the JQL field is updated in this way and if the indexing is not finished while we are calculating the issue, JQL does not work correctly because the index of the issue hasn’t been completed yet. There may be times when Time to SLA has trouble keeping up with issue updates due to numerous automations. This could lead to problems with calculations and the wrong information being shown on the SLA Panel. Enabling the Asynchronous Update will get rid of such problems.
This only happens in some rare instances. To remedy this, we’ve created the Asynchronous Update. When you enable this, here’s how the your issue will be calculated:
Time to SLA will save the event in the database. Depending on how often your task is updated, Time to SLA will calculate the issue and the SLA with a 1-minute delay.
We recommend only ticking this box if any field within the SLA's JQL condition might be updated during the workflow transitions. If you enable this option, then Time to SLA will make calculations after issue events occur. You might expect better issue load times, but there will be a delay of about one minute before seeing the changes on SLAs. There may be times when Time to SLA has trouble keeping up with issue updates due to numerous automations. This could lead to problems with calculations and the wrong information being shown on the SLA Panel. Enabling the Asynchronous Update will get rid of such problemsIn a nutshell, we allow time for the issue to be indexed and start processing after 1 minute.
SLA configuration’da JQL alanı var. Normalde eğer bu JQL alanı, issue’daki herhangi bir transition sırasında update edilirse, normalde bir sıkıntı olmamasını bekleriz. Ancak Jira’da race condition'ına takılabiliyoruz. Issue’nun indexlenmesi , biz calculation’a başladıktan sonra tamamlanması durumu var. Bu JQL’deki field eğer bu şekilde update edilirse, biz issue’da calculation yaparken indexlemesi bitmediyse, JQL doğru çalışmamış oluyor çünkü daha issue’nun index’i en son haline gelmemiş oluyor. JQL Search de index üzerinden çalışıyor.
...