SLA not being updated after setting priority

[Alejandro Álvarez]

Hi all,

Context: By default, when a Bug is created by clients in JSM, priority is not defined. Once we analyse the ticket, we define the priority.

Problem: SLA is not being updated to the one corresponding to the set priority.

I'm not sure if the issue is related to not re-calculating the new SLA or that from the start the conditions of our SLA are not set correctly and it's always landing on the default SLA.

The filter conditions that match with the ticket (Type = Bug AND priority = Minor)

The ticket itself showing SLA 86 h.

The SLA setup. Issuetype = Bug (Issuetype and type fields are the same) and Priority = Poco Importante (is the transaltion to Minor) should have 72 h SLA. 

Can you help me figuring our why the ticket is taking 86h of SLA instead of 72h?

Thanks and regards

[Ken Poon]

I am having the same issue with a french JSM, were you able to resolve this?