Use cases and recipes


Overview

This page provides ready-to-use configuration recipes for common time-tracking scenarios. Each recipe includes the field type, settings, events, and goals needed to implement the use case.


Response Time SLA

Goal: Track how long it takes to respond to a customer request, with different SLA targets based on priority.

Field type: Timer

Configuration:

Setting Value
Start Events STATUS_TO: “Open” or ISSUE_CREATED
Stop Events CREATE_FIRST_PUBLIC_COMMENT
Pause Events STATUS_TO: “Waiting for Customer”
Calendar Business Hours (e.g., Mon-Fri 9:00-18:00)
Display Mode LEFT_TIME_ICON

Goals (JQL-based):

Priority JQL Goal
Highest priority = Highest 1h
High priority = High 4h
Medium priority = Medium 8h
Default - 24h

How it works: The timer starts when the issue is created and counts down toward the priority-based goal. When a public comment is posted, the timer stops. If the response takes longer than the goal, the issue is marked as Failed.

JQL to find breached SLAs:

"Response SLA.StateValue" = "Failed"

Resolution Time SLA

Goal: Track total time from issue creation to resolution, with SLA targets.

Field type: Timer

Configuration:

Setting Value
Start Events ISSUE_CREATED
Stop Events RESOLUTION_SET
Restart Events RESOLUTION_REMOVED
Pause Events STATUS_TO: “Waiting for Customer”
Calendar Business Hours
Display Mode TIME_SPENT_ICON

Goals:

Priority JQL Goal
Highest priority = Highest 4h
High priority = High 1d
Default - 3d

How it works: Starts at issue creation, pauses when waiting for the customer, stops when resolved. If the resolution is removed (issue reopened), the timer restarts - a restart from Completed or Failed works without Allow restart from any state. Goals vary by priority.


SLA by Customer Tier

Goal: Apply different SLA calendars based on a customer’s support tier (e.g., Gold customers get 24x7 support, Silver gets business hours).

Setup:

  1. Create calendars:
    • “Gold - 24x7” (every hour counts)
    • “Silver - Business Hours” (Mon-Fri 9:00-18:00)
    • “Bronze - Extended Hours” (Mon-Fri 8:00-20:00)
  2. Create a Calendar Select field called “SLA Calendar”
    • Available calendars: Gold, Silver, Bronze
    • Default: Silver
  3. Create a Timer field “SLA Timer”
    • Calendar Field: “SLA Calendar”
    • Start/Stop/Pause events as needed
    • Default goal: 8h

How it works: When an agent sets the Calendar Select field to “Gold - 24x7” on a VIP customer’s issue, the timer uses 24x7 hours for calculation. Regular issues use the default “Silver” calendar.

See Calendar Select field for setup details.


Tips for building your own recipes

  • Start simple: begin with a single start and stop event. Add pause and restart events only when needed.
  • Test with one issue: configure the field, run recalculation for a single issue, and verify the result before rolling out to all projects.
  • Calendar choice matters: use a business-hours calendar when you want to exclude non-working time. Use 24x7 when total elapsed time matters (e.g., customer waiting time).
  • Combine fields: you can have multiple time-tracking fields on the same issue. For example, one timer for Response SLA and another for Resolution SLA.