Who can use this?
Player card shows recent work and long-term data to identify recent problem spots, historical patterns, and areas for growth.
Find Player card under the 1-1 Coaching section in the left navigation.
Who uses Player card?
Use Player card to identify Flow data points where you'd like to seek additional context. Combine data-driven insights with user context to make your 1:1s more productive.
If you're a manager, scrum master, or team lead, the Player card report helps you:
- Understand an individual's strengths in relation to their teams.
- Identify areas of improvement for your engineers.
- Plan how you can support the individuals on your team to do their best work.
If you're an engineer, Player card helps you:
- Understand how your work relates to others on your team.
- Have a data-driven conversation with your manager about where you're excelling and what your blockers might be.
- Track your progress over time.
What data does Player card show?
Player card tracks five sets of metrics: Coding metrics, Submit fundamentals, Review fundamentals, Activity, and Pull requests.
Each section highlights different metrics and ways to look at an engineer's work. Learn more about Flow metrics and how they're calculated.
Player card fundamentals
The fundamentals sections show a user's metrics in relation to their team broken down by quartile. Hover over the icon to the right of a metric to see a chart of that metric's data.
Player card fundamentals includes Coding metrics, Submit fundamentals, and Review fundamentals reports. Each section features metrics from its respective report.
Coding metrics includes:
- Coding days
- Commits per day
Submit fundamentals includes:
- Comments addressed
- Unreviewed PRs
Review fundamentals includes:
- Reaction time
- Review coverage
Note: The Submit and Review fundamentals sections only show metrics based on merged PRs.
Activity helps you spot patterns and trends within your users' activity. Use the Show filter to view Code commits, Merge commits, PR activity, PR comments, or Ticket activity.
Use the Weekends toggle to choose whether the chart displays weekend activity. Click the blue back arrow on the left to display activity from previous weeks.
Hover over an icon to view detailed information about that activity.
Pull requests shows PRs from the specified time frame.
To narrow down PRs, use the Sort by dropdown menu to seelct a sort option such as, Recently opened, Biggest, or Least activity. Then, choose a PR status such as All, Opened, Merged, Closed, or Deleted. Use these filters to see exactly which pull requests you're interested in.
Hover over a pull request to view more information about it, such as recently committed code or comments. Click a pull request to see the pull request's number and a link to view the pull request itself.
How do I choose which information Player card shows?
Use filters to customize the information in Player card. Filter by Repo, Date Range, and Targets.
To view activity from a repo or set of repos, click Repo and select the repos you're interested in. Use the search feature to select repos based on name or tag.
Use Player card to see a developer's progress over time. Click Date range to only see data for a specific period of time.
On the Date ranges tab, click a preset date range such as trailing 14 day period or year to date to set it. Click Custom or use the provided calendar to create your own date range.
Use the Sprints tab to show activity during a specific sprint. Learn more about setting up custom date ranges and calendars.
Click on or off next to targets to choose whether or not to view the fundamental reports sections' custom targets.
Tip: Targets are On if there are dotted lines on the charts in the fundamentals sections. Settings for Repos, Date ranges, and Targets do not change if you switch which user you're looking at.
How do I find a specific user and filter their data?
To find another user's Player card:
- Click on the current user's name to bring down a dropdown menu.
- Search for a name using the text box or user list.
Alternatively, find a user by cross-linking them from another report. Learn more about cross-linking users in reports.
Once you've chosen a user, use the compared to field to select which team you want to compare that user to. Click Included or Excluded to choose whether or not to include nested teams.
Note: Player card doesn't compare a user to the whole organization. Its intended use is to facilitate conversations about team contribution. If you'd like to understand how a user relates to all engineers in the organization, create a team that contains every engineer.
If you need help, please email email@example.com for 24/7 assistance.