Skip to main content
All CollectionsAnalytics
Contributions Analytics
Contributions Analytics
Updated over a week ago

Permissions

Org Admin

Team Manager (for assigned team)

Org Contributor

External Contributor

View

View

View

No access

Introduction

This article will guide you through the devActivity Contributions Report, a powerful tool for analyzing developer activity within your repositories. This report provides valuable insights into the quantity and types of contributions made by developers over time. You can use this information to identify top performers, track contributor engagement, and understand the overall health of your projects.

Contributions Report

  • Access: Navigate to the "Analytics" section and select the "Contributions" tab.

  • Purpose: Generate comprehensive report for your request.

Filtering and Sorting Data

The Contributions Report offers flexible filtering and sorting options to refine your analysis:

  • Repositories: Select a specific repository or view all repositories.

  • Contributor: Choose a specific contributor or view data for all contributors.

  • Period: Select a predefined time period (e.g., 3 months, 6 months, 12 months) or customize a specific date range.

You can sort the data by various metrics, including:

  • Contributor: View contributions in alphabetical order.

  • Experience Point Trend: Sort contributions by XP earned.

  • Contribution Score by Contributor: Sort contributions by the total XP earned by each contributor.

  • Contribution Heatmap: Sort contributions by the date they were made.

Understanding the Data

The Contributions Report presents developer activity through three key visualizations:

Experience Point Trend

This chart displays the trend of experience points (XP) earned over weekly periods. Each bar represents a week, with the height indicating the total XP earned. The bars are segmented by color to represent different activity types:

  • Pull Requests

  • Commits

  • Code Reviews

  • Issues

Hovering over a bar reveals a tooltip with a breakdown of XP earned for each activity type within that week.

Contribution Score by Contributor

This section provides a visual comparison of experience points (XP) earned by different contributors across various activity types. It uses horizontal bars to represent each contributor, with the length of the bar corresponding to the total XP earned. Within each bar, different colors represent XP earned from specific activity types:

  • Blue: Pull Requests

  • Green: Commits

  • Light Blue: Code Review

  • Orange: Issues

Hovering over a bar or segment reveals a tooltip with detailed information, such as the total XP for the contributor, the number of Pull Requests, Commits, Code Reviews, or Issues, and the XP earned for each event.

Contribution Heatmap

This feature visually represents a user's daily contributions over the past 12 months using a color-coded grid. Each column represents a month, and each row represents a day of the month. The intensity of the green color within each cell corresponds to the amount of XP earned on that specific day. Darker green indicates higher XP earned. Hovering over individual cells reveals a tooltip with the date and XP earned for that day.

Exporting and Sharing Data

You can easily export the data from the Contributions Report for further analysis or sharing:

  • Export to CSV: Click the Export to CSV button to download the data in a spreadsheet format.

  • Copy to Clipboard: Click the Copy Data button to copy the data to your clipboard.

AI Insights (Premium Feature)

Premium users have access to AI-powered insights derived from the Contributions Report data. These insights provide valuable information for optimizing team performance and making data-driven decisions.

This comprehensive guide provides a detailed understanding of the devActivity Contributions Report and its key features. By leveraging this report, you can gain valuable insights into developer activity, track progress, identify top performers, and make informed decisions to enhance the productivity and efficiency of your development teams.

Get answers to the following questions:

  1. How are the activities/contributions going (trending up or down) for the organization/team?

  2. What team/contributor is below average? What is above?

Recommended actions:

  1. Discuss on retrospective or/and on 1-2-1s:

    • How to help contributors below average and with trends strongly going down. Keep in mind day-offs, vacations, etc.

    • The possibility to scale the actions made trends go up for specific teams/contributors.

  2. Actualize the Alert thresholds for instant notifications about activity bottlenecks.

Contributions

Get answers to the following questions:

  1. What type of contribution is dominating for a specific team/contributor?

  2. Do you need to rebalance the attention of contributors to other types of contributions?

  3. Do you have enough team members to perform Code Review efficiently?

  4. Are commits and pull requests balanced? Or do you need to correct the work chunks teams are operating?

  5. Is there a known reason for someone strongly ahead or behind the rest of the team?

Recommended actions:

  1. Discuss the insights on retrospective.

  2. Make sure all team members are familiar with the analytics.

  3. Ask for the reasons and proposals from contributors strongly below average.

  4. Use team and individual Challenge thresholds to set appropriate goals and forward attention to necessary types of contributions.

  5. Make sure alert thresholds are actualized to get the instant notification and make corrections right away not at the end of the period.

Daily Contributions over the Year

Get answers to the following questions:

  1. What days are likely to be more/less active?

  2. What period likely was a vacation period?

  3. How does the team structure impact the activity over a longer period?

Recommended actions:

  • Consider the meetings list for the less active days of the week.

  • Plan the vacation schedule.

Recommendations

  • Consider challenges related to XP (Contributions Score) to impact the metrics

Questions, Ideas, Improvements

Did this answer your question?