SLA counter modification on an issue

[Shawn Jamison]

I have 4 different SLA's in a large project where 2 to 4 automations will comment or transition to close the issues based on which SLA's have been breached or are about to breach.

My question is on an issue where a 40 hour SLA is active is there a way I can advance the counter on an issue to trigger the SLA breached trigger of an automation? 

I want to be able to test automations with SLA's and automation triggers that have between 20 and 40 business hours without having to wait 20 to 40 business hours

Thanks

[Ste Wright]

Hi @Shawn Jamison 

Not that I know of, the SLA counter is basing itself on a period of time, and needs to count through that to zero.

Couldn't you just shorten the time spans for testing?

Ste