What advantages does SLA Breakdowns have compared to the [task_sla] table and metric definitions?

[SB87]

I've come across SLA breakdowns and can see an SLA breakdown can be set against an SLA record, but I'm failing to understand the advantages compared to data already recorded in the [task_sla] table or available through the use of metric definitions.

For example, SLA Breakdowns by Assignment will give you a clear understanding of who worked on the task (and when), amount of SLA time used, how much remains, etc.

Is this not already achievable by using the task_sla table? And if we wanted to build a picture of who worked on a task then couldn't we simply set up a metric definition for assignment group changes?

Perhaps I am missing something obvious, but if anyone can shed some light it would be much appreciated. 

[AndersBGS · Accepted solution]

Hi @SB87 ,

the obvious is, that if you add the SLA_breakdown, then you don't need the metric and compare with the task_sla table, but you will have it all through the SLA table. Furthermore, if the same assignment group is hit twice, it will be grouped in the sla_breakdown but will be separate in the metric. 

If my answer has helped with your question, please mark my answer as accepted solution and give a thumb up.

best regards

Anders

[SB87]

Thanks for confirming my understanding is correct, Anders. Much appreciated.