Timepiece - Time in Status for Jira

Overview

Timepiece_Colorfull_Horizontal_Logo (2).png

Timepiece - Time in Status for Jira is an advanced Jira reporting and workflow analytics app that helps teams analyze issue histories, calculate SLA-style metrics, and improve operational visibility inside Jira Cloud.

The app generates reports directly from Jira issue history data without requiring workflow changes or additional automation rules. Teams use Timepiece to measure workflow efficiency, identify bottlenecks, analyze delivery performance, and calculate metrics such as Lead Time, Cycle Time, Resolution Time, and Response Time.

Time-Based Jira Reporting

Timepiece provides multiple report types for analyzing issue durations and workflow activity.

The most commonly used report is the Status Duration Report(Time in Status Report), which shows how long issues stayed in each workflow status throughout their lifecycle.

Other available report types include:

  • Duration Between Statuses Report

  • Assignee Duration Reports

  • Group Duration Reports

  • Any Field Duration Report

  • Count Reports

  • Transition Date Reports

Learn more about:

Lead Time, Cycle Time, and SLA Metrics

Timepiece can be used to calculate common engineering, support, and service management metrics directly from Jira issue history.

Teams commonly use Timepiece for:

  • Lead Time reporting

  • Cycle Time analysis

  • Resolution Time tracking

  • Response Time calculations

  • SLA-style workflow reporting

  • Queue and waiting time analysis

Unlike Jira SLA counters, Timepiece can analyze historical issue data and generate reports for past workflow activity.

Grouping and Aggregation

Timepiece supports advanced grouping and aggregation capabilities.

Reports can be grouped by Jira fields such as assignee, sprint, customer, request type, issue type, project, component, and labels. Time-based grouping options such as week, month, and year are also supported.

This allows teams to analyze trends over time and compare workflow performance across projects and teams.

Learn more:

Custom Calendars and Business Hours

Timepiece supports custom calendars for more accurate business-hour and SLA-style calculations.

Teams can configure:

  • Working days

  • Working hours

  • Time zones

  • Holidays

  • Non-working periods and lunch breaks

Reports can then be calculated based on working time instead of raw 24/7 durations. This is especially useful for support teams, service desks, and globally distributed organizations.

Learn more:

Scheduled Reports

Timepiece supports scheduled report generation and automated report delivery.Teams can configure reports to run automatically and deliver results on a recurring schedule.

Scheduled reports can be used for:

  • Weekly SLA summaries

  • Operational KPI reporting

  • Sprint performance reviews

  • Management reporting

  • Automated workflow monitoring

Learn more:

Exporting Reports

Timepiece reports can be exported for external analysis and sharing. Exported reports can be used in spreadsheet tools, BI platforms, and internal reporting workflows.

Learn more:

REST API and External Reporting

Timepiece provides REST API support for external reporting and automation scenarios.The REST API can be used to retrieve report results programmatically and integrate Timepiece data with third-party platforms and internal systems.

Common use cases include:

  • BI integrations

  • Automated reporting pipelines

  • Custom dashboards

  • External analytics platforms

Learn more:

Timepiece AI Assistant

Timepiece includes an AI-powered assistant that helps users generate reports and access insights more efficiently.

The Timepiece Assistant allows users to interact with the app using natural language instead of manually configuring reports step by step.

Users can ask questions such as:

  • “Show average resolution time by sprint”

  • “Calculate lead time for resolved issues”

  • “Display issues waiting for customer response”

The assistant helps reduce configuration effort and makes advanced reporting more accessible to both technical and non-technical users.

Learn more: