Chancing SLA conditions

Eddy Krijnen August 17, 2021

I have placed new conditions in my SLA. However, the system does not recalculate everything. It also seems random. How is that possible? see new SLA conditions Fig 1 and see report: Fig 2. There are still time units of 8 hours in between, while I have entered a new condition of 4 hours.

 

Time to first response 4h.PNG

Fig 1

 

 

Rapport SLA.PNG

Fig 2

 

2 answers

0 votes
Phill Fox
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 17, 2021

Hi @EdD

When you change an SLA they do recalculate but if you have a lot of tickets or very complex SLAs this can take some time to complete the recalculation. I have also observed that it is best to make all SLA changes in a consolidated manner rather than a piecemeal change at a time.  You can always look at a ticket and it will force a recalculation of the SLA for that single ticket. This is maybe why you saw one that was already correct? 

Phill 

0 votes
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 17, 2021

I'm not quite seeing the issue but probably missing your point? So for issues that are already complete they will not change. For issues that are not yet done they should re-calculate. In your image there appears to be a single issue it is not done yet. It shows that it has exceeded the SLA but 8 hours 35 minutes. So for that issue my question is has the issue been open for 12 hours and 35 minutes?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events