Versions Compared

Old Version 4

changes.mady.by.user Derya Özdemir

Saved on

compared with

New Version Current

changes.mady.by.user Derya Özdemir

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel
panelIconIdatlassian-info
panelIcon:info:
bgColor#F4F5F7

This page is for about Time to SLA for Jira Server usersOn-Prem.

Problem

SLA calculation problems occur after particular transitions.

Time to SLA has issue listeners which 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.

Never Listening

Since the events listed below are not stated directly in SLA contracts, TTS listeners never listen to them.

  1. Work Logged On Issue

  2. Work Started On Issue

  3. Work Stopped On Issue

  4. Issue Worklog Updated

  5. Issue Worklog Deleted

Special Events

TTS listens to the following events if you use comment actions in SLA definitions. But However, they should not be used in workflow transitions to get accurate SLA data.

  1. Issue Commented

  2. Issue Comment Edited

  3. Issue Comment Deleted

Solution

Do not use the events listed above in your workflow post functions.