Report question
An original support lead asks for the median full-resolution time of tickets solved in February. This differs from asking about tickets created in February. Define the date cohort, metric, grouping and aggregation before reading a number.
Zendesk’s full-resolution recipe measures from creation to the last solve. Its example uses the median and allows a created-date filter. That is one report configuration, not a rule that every resolution request must use the same cohort.
Worked population example
Ticket A was created January 31 and last solved February 3. Ticket B was created February 2 and remains open. Ticket C was created February 4 and last solved February 5. For a February solved cohort, A and C qualify; B does not have a completed full-resolution duration. Treating B as zero would invent a successful resolution.
After a reopen, first solve and last solve can differ. An equal chart total does not establish that the right records entered the median. Inspect source IDs and timestamps.
Report definitions
Retain the date range, cohort, aggregation, grouping and included records. The local Zendesk course calculates a disclosed reporting subset from fictional ticket events; it is not the full Explore query builder or a live dashboard. Pair the report with SLA policy evidence without treating reporting metrics and SLA fulfillment as identical.