Team-wise Productivity Leaderboard Dashboard Implementation
Summary
Introduce a Team-wise Productivity Leaderboard Dashboard in the GitLab Compliance & Analytics Tool.
This feature provides aggregated team-level and individual-level productivity insights including commits, merge requests, and issues. It improves contribution tracking, transparency, and performance visibility across teams.
Problem to Solve
As a mentor or team lead, I want to view team-wise and member-wise productivity metrics so that I can monitor contributions, evaluate performance, and identify active contributors efficiently.
Currently, the tool does not provide a consolidated team-based analytics view.
Intended Users
Mentors Team leads Admins Contributors Batch coordinators
User Experience Goal
Users should be able to:
Select a team from a dropdown menu
View aggregated team productivity metrics
See a ranked leaderboard based on commits
Select an individual member to view detailed performance metrics
The interface should be intuitive, responsive, and visually structured.
Proposal
Implement a new dashboard mode called Team-wise Productivity.
Feature flow:
User selects a team from the dropdown.
The system fetches productivity data for all members in that team.
Display aggregated metrics:
Total commits
Total MRs merged
Total issues closed
Display a leaderboard sorted by commits.
Provide a bar chart comparison of member commits.
Allow individual member selection for detailed metrics view.
Backend integration:
Use get_team_productivity() for aggregation.
Use get_user_productivity() for individual metrics.
Frontend implementation:
Streamlit UI with dropdowns, metrics, tables, and charts.
Loading states and proper error handling.
Further Details
Supports multiple teams including Dev 3, Trinity, Sudo, Synergy Six, Code Dev, and SPK.
Ensures no disruption to existing compliance and user profile modes.
Adds structured analytics capability to the tool.
Improves decision-making visibility for mentors.
Security or Permissions Considerations
Requires valid GitLab Personal Access Token.
Token must include:
api
read_api
read_user
read_repository
No additional permissions beyond standard GitLab API access.
No sensitive data stored persistently.
Documentation Impact
Documentation updates required:
README (new feature description)
Setup guide (GitLab token configuration)
Usage instructions for Team-wise Productivity mode