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, and events needed to implement the use case.


Development Cycle Time

Goal: Measure how long issues spend in active development (from “In Progress” to “Done”).

Field type: Stopwatch

Configuration:

Setting Value
Start Events STATUS_CATEGORY_TO: “In Progress”
Stop Events STATUS_CATEGORY_TO: “Done”
Pause Events STATUS_TO: “Blocked”, STATUS_TO: “In Review”
Calculate Type ALL_STARTS
Calendar Business Hours
Display Mode TIME_SPENT_ICON

How it works: The stopwatch starts when the issue enters any “In Progress” category status and stops when it reaches “Done.” Time spent in “Blocked” or “In Review” is excluded via pause events.

JQL to find slow issues:

"Cycle Time.TimeInHoursValue" > 40 AND "Cycle Time.StateValue" = "Stopped"

Time to First Response

Goal: Track how long until someone first responds to an issue (any comment).

Field type: Stopwatch

Configuration:

Setting Value
Start Events ISSUE_CREATED
Stop Events FIRST_COMMENT
Calculate Type ONLY_FIRST_START
Calendar Business Hours
Display Mode TIME_SPENT

How it works: Starts when the issue is created, stops at the first comment. Uses ONLY_FIRST_START to ensure the value is fixed after the first response.


Waiting Time Tracking

Goal: Track total time an issue spends waiting for a customer response.

Field type: Stopwatch

Configuration:

Setting Value
Start Events STATUS_TO: “Waiting for Customer”
Stop Events STATUS_FROM: “Waiting for Customer”
Calculate Type ALL_STARTS
Calendar 24x7 (waiting time counts 24/7)
Display Mode TIME_SPENT

How it works: Every time the issue moves to “Waiting for Customer,” the stopwatch starts. When it leaves that status, the stopwatch stops. ALL_STARTS accumulates time across all waiting periods.


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 stopwatch for development cycle time and another for waiting time.