Documentation

Reports & Insights

Understand your team's velocity and identify bottlenecks with data-driven reports.

Overview

The Reports section translates raw Jira data into actionable insights. By analyzing ticket throughput, cycle times, and automation impact, you can make more informed decisions about your engineering resources.

Key Reports

1. Velocity Tracking

Measure how much work your team is completing over time:

Throughput by Sprint: Count of tickets completed per interval.
Point Velocity: If using story points, see the average points delivered.
Consistency Score: Measures the predictability of your team's output.

2. Cycle Time Analysis

Identify where tickets are getting stuck:

Lead Time: Time from creation to completion.
Cycle Time: Time from starting work ("In Progress") to completion.
Bottleneck Detection: See which status (e.g., "Code Review", "QA") tickets spend the most time in.

3. AI Impact Report (Pro Feature)

Visualize the value of Ticket Mate's AI:

Time Saved: Estimated hours saved by AI ticket enhancement.
Description Quality: Comparison of manually created vs. AI-enhanced tickets.
Automation Efficiency: Number of manual status updates avoided by our rules engine.

Using Insights

For Standups

Use the Cycle Time report to identify tickets that have been in "Code Review" for more than 48 hours.

For Retrospectives

Review the Velocity report to see if team changes or process adjustments (like adding new automation rules) have positively impacted throughput.

For Resource Planning

Use the Throughput trends to project when upcoming milestones will be reached based on historical performance.

Best Practices

Consistent Statuses: Ensure your team uses the same status workflow to keep reports accurate.
Point Alignment: If using points, ensure all stories are pointed before being moved to "Done".