---
title: "SLA calculation issues during workflow transitions"
canonical: "https://support.appfire.com/space/TTS/49741858/SLA%20calculation%20issues%20during%20workflow%20transitions"
format: markdown
---
> Macro (aura-html)

## <span style="color: #0e101a">Problem</span>

<span style="color: #000000">SLA calculation problems occur after particular transitions.</span>

<span style="color: #000000">Time to SLA has issue listeners that listen to Jira events fired via workflow post functions. For better performance purposes, TTS does not listen to all events. If you use event types that TTS does not listen to in workflow post functions, then SLA calculations are not processed via TTS listeners, and SLA calculation problems occur.</span>

## <span style="color: #0e101a">Never Listening</span>

<span style="color: #000000">Since the events listed below are not stated directly in SLA contracts, TTS listeners never listen to them.</span>

1. <span style="color: #000000">Work Logged On Issue</span>
2. <span style="color: #000000">Work Started On Issue</span>
3. <span style="color: #000000">Work Stopped On Issue</span>
4. <span style="color: #000000">Issue Worklog Updated</span>
5. <span style="color: #000000">Issue Worklog Deleted</span>

## <span style="color: #0e101a">Special Events</span>

<span style="color: #000000">TTS listens to the following events if you use comment actions in SLA definitions. However, they should not be used in workflow transitions to get accurate SLA data.</span>

1. <span style="color: #000000">Issue Commented</span>
2. <span style="color: #000000">Issue Comment Edited</span>
3. <span style="color: #000000">Issue Comment Deleted</span>

## <span style="color: #0e101a">Solution</span>

<span style="color: #000000">Do not use the events listed above in your workflow post functions.</span>