Additional Assignees and SLA Impact - Please help

[KFry]

We are trying to move to more out of the box technology and best practices for ITSM.

Currently, our analysts add a large group to the "Additional Assignee" field.

We want to move into creating incident tasks to create clearer ownership and to focus on SLAs.

I think adding additional assignees will impact the SLA, they say they can add themselves and take themselves off to track time if they need to provide triage/oversight on the ticket and they can track their time specifically to do that and it doesn't impact the SLA.

I need an expert or documentation to help me understand if the SLA is only triggered by the primary/first assignee and if the additional have any impact.

[Brian Lancaster]

The only thing that will affect SLAs is there configuration. Meaning Start condition, Pause conditions, stop conditions, and reset conditions. 

[KFry]

So we track SLA by assignment group. So if an incident is assigned to the assignment group (and an individual within) it doesn't matter who the additional assignees are and will just track to see how long it takes to completion and count towards the assignment group?