Team Insights

Team insights provide detailed analytics about how your team works, what you focus on, and how patterns change over time. These metrics are exclusively available to team members and help identify strengths, trends, and improvement opportunities.

Insights are one of the key benefits of creating or joining a team. Solo users cannot access insights until they're part of a team, even if they're alone in that team.

Accessing insights

Choose from preset ranges like "This Week," "Last 30 Days," "Last Quarter," or "Last Year" to analyze different time windows. Set your preferred timezone for accurate time-based analysis, ensuring data aligns with your team's working schedule.

Switch between team-wide insights and individual team member analysis to understand both collective patterns and personal contributions.

Activity and work distribution

See how your team's completed tasks break down across six categories: Development, Maintenance, Collaboration, Planning, Learning, and Administrative work.

Activity trends

Activity trends reveal how your team's focus shifts over time, displaying stacked percentages of each activity type across different periods. Track the percentage of work dedicated to feature building over time, helping identify whether you're maintaining a healthy balance between new development and other activities.

Maintenance trends highlight when your team spends more time on bug fixes, refactoring, and system maintenance versus new feature development.

Task and code analysis

Task topics automatically detect and rank the most significant work areas based on completed tasks, weighted by complexity to reflect actual effort invested.

Development distribution

Development distribution categorizes work as Frontend, Backend, Infrastructure, Documentation, Bug Fixes, New Features, or Refactoring. Tasks can have multiple labels, so percentages may exceed 100%.

Code languages show the percentage of lines changed per programming language, reflecting your team's technology footprint and focus areas. Radar charts provide alternative visualizations for activity, task type, and language distributions, making it easier to spot patterns and imbalances.

Pull request metrics

Lead time distribution tracks how long pull requests take from creation to merge, showing what percentage complete within 1 day, 7 days, or longer.

Lead time trends

Lead time trends monitor whether your PR completion times are improving or degrading over time, with average, median (P50), and P75 percentile tracking. PR volume trends show how many pull requests your team creates and merges over time, indicating development velocity.

Cycle time phases break down where time is spent in the PR process, helping identify bottlenecks in review, testing, or deployment phases.

Using insights effectively

Regular reviews during team retrospectives help identify patterns, celebrate improvements, and address concerning trends. Balanced workload analysis reveals whether team members are overloaded with specific types of work or if the team needs to adjust focus areas.

Process improvements become visible through metrics like PR lead times, helping teams optimize development workflows. Goal tracking enables data-driven discussions about productivity, code quality, and team health based on concrete metrics rather than subjective impressions.

For detailed information about specific metrics, calculations, and actionable recommendations, see Team Insights. You can also explore Understanding Metrics for technical details about how insights are calculated.