Note: Knowledge sharing is only available in Flow Enterprise Server. To access the same information in Flow Cloud, use Review collaboration and Team health insights.
Users share knowledge and develop familiarity across a codebase by reviewing PRs for their teammates. The Knowledge sharing report shows the distribution of code review activity across team members.
This allows you to see what context your teammates share with each other and prevents knowledge silos from developing.
The Knowledge sharing index measures how broadly information is being shared within a team. The higher the sharing index, the more your team is sharing with each other.
Use this report to increase knowledge sharing across a team and broaden engagement in the review process.
In this article
Finding the Knowledge sharing report
To find the Knowledge sharing report:
- Click Reports in the top navigation.
- In the left navigation under Team processes, click Knowledge sharing.
Using the Knowledge sharing report
The Knowledge sharing report helps identify best practices and collaboration patterns on your teams.
Team leads and managers use the Knowledge sharing report to:
- Identify best practices and collaboration patterns on their teams.
- Increase knowledge shared and engagement during the review process.
- Open discussions with team members about team collaboration.
Tracking how well your team shares knowledge
The Knowledge sharing graph shows how well your team shares knowledge. Compare this to the Sharing target to track knowledge sharing growth within your team. Hover over data points to view more details, including:
-
PRs: number of PRs
-
Sharing index: Knowledge sharing index value for the date
-
Available reviewers: number of users who commented on a PR or committed code
-
Active reviewers: number of users who reviewed a PR
-
Submitters: number of users who submitted a PR
Use this graph to see your team’s average Sharing index and evaluate how their Knowledge sharing is trending compared to their Sharing target. Learn more about setting targets.
Most teams’ average Sharing index ranges from 0.2 to 0.4. Encourage your team members to review more PRs for more teammates to increase the Sharing index.
Viewing code review activity distribution across team members
The Review radar graph shows which members collaborate on PRs and how many PRs they review within the selected time period.
Use the x axis to view how many different users’ PRs were reviewed. Use the y axis to view the total number of PRs the user reviewed.
Hover over a bubble to view users and who they collaborated with. Click a user to view their details.
Review radar shows how code reviews are distributed throughout the team.
The graph shows how many reviews and reviewees a user has. Users in the top right of Review radar are reviewing several PRs for multiple teammates.
Tip: Users in the top right corner of the Review radar are often impactful knowledge-holders in your teams. Talk with them to find ways to help pass along this knowledge to other reviewers and reduce the review burden on your most impactful team members.
The thickness of the line connecting two people is a visual indication of how many of their PRs they've reviewed. A thicker line indicates more reviewed PRs.
Solid circles represent users on a team. Hollow circles represent users not on the team.
Finding more details in Review collaboration
Refer to the Review collaboration report to view the specific number of PRs users reviewed for another user.
To get more details on a user in the Review collaboration report:
- Click a user's bubble in Review radar.
- Click Filter by user in....
- Click Review collaboration.
- Click Reviewer.
Use insights from Review radar to find where you can increase knowledge shared and engagement in the review process.
For example, you may expect to see senior engineers reviewing more PRs and pairing with newer engineers, though it might vary depending on the context of the user and their projects. If these trends aren’t aligning with your expectations, start a conversation with your team focused on creating better collaboration practices.