Added SLAs to SDCLOUD project but not all issues yield their respective SLAs

[Rosa M Fossi]

Hello Community,

From what I've read in forums if I apply SLA's into a Service Desk Cloud project that has never had SLAs before, it should still calculate the respective SLA's per issue (the data/transitions/dates exist in the DB after all!). 

I've added a simple SLA: 

Start / Begin Count When Entered Status: Technical Review
Pause on  No Pauses
Stop / Finish Count when Comment: For Customers; Entered: Status Cancelled, Client Support, Done, Development. 

issuetype in (Bug, Support) and priority = high | Goal 2h | 8am-5pm EST calendar

Is my assumption wrong?  Is my SLA setup wrong?   

Any insight would be greatly appreciated  

[Ismael Jimoh]

Hi @Rosa M Fossi 

To my knowledge already closed issues are not recalculated automatically.

The SLAs for these are the ones active while work was being done on the issue.

Your new SLA would only count on these issues when they enter the start state again.

Cheers

[Rosa M Fossi]

Thanks Ismael... 

The "closed" issues logic makes sense.   I'm not sure I understand your next statement though

Your new SLA would only count on these issues when they enter the start state again.

Are you talking about closed issues only?   Because I'm not looking for SLA data in already closed issues.    I would be satisfied with SLA's being calculated on currently open issues.  The problem is that even though I know for a fact that some of the issues have transitioned through the status / priority stated in the SLA, no numbers are being returned....