Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Button handy
blankfalse
color#0052CC
nameOn-Prem
linkhttps://appfire.atlassian.net/wiki/spaces/TTS/pages/46661816/The+SLA+History
width85
Button handy
blankfalse
color#EBECF0
nameCloud
linkhttps://appfire.atlassian.net/wiki/spaces/TTSC/pages/35456368/The+SLA+History
width84

Check out the example below:

...

1. All – All actions taken and comments sent for the issue can be found here.

2. Comments – You can see all of the comments made on the issue.

3. Work log – This enables you to log your work.

4. History – The issue’s history is recorded here; however, it doesn’t allow you to see the sent comments.

5. Activity – A look back on what has happened on the issue.

6. SLA Overview – This gives you a quick look into the active SLAs on the issue, allowing you to see the SLA's name, its working duration, pause duration, its goal, and the calendar associated with it.

...

7. SLA History – You can see all of the issue’s SLA History here, and export it in .xlxs or .pdf format. Check out an example below:

...

Panel
panelIconIdatlassian-info
panelIcon:info:
bgColor#F4F5F7

This page is about Time to SLA for Jira On-PremData Center. UsingJira Cloud? Click the Cloud button above.

...

here.

The SLA History tab in the Time to SLA app provides detailed insights into the lifecycle of SLAs. It organizes SLA states into cycles, allowing you to track performance, identify trends, and pinpoint areas for improvement.

To access the SLA History tab:

  1. Navigate to an issue.

  2. Click the SLA History tab.

  3. Use the dropdown menu to view all SLAs associated with the issue and select one to explore its details.
    You can check the Overall Details box to display time details.

    Image Added

SLA cycles

Each cycle consists of a start and end condition. By examining your SLA history, you can easily see how long people spent between those conditions.

  • The time between these start and end conditions shows how long it takes to complete a cycle (that is, elapsed time).

  • When an SLA is stopped, its current cycle is marked as Met or exceeded based on its completion status.

  • If an issue is reopened after an SLA cycle ends, a new cycle automatically starts.

The reset function isn’t a start condition, which means it cannot start a new cycle. If you want a reset to trigger a new cycle, the SLA’s end and reset conditions should be the same. If you reset an SLA that has already been completed, you will be able to start a new cycle with a reset condition.