Awesome Graphs is one of our most popular add-ons. It’s a solution that extends Bitbucket, a platform that teams use to host Git repositories and collaborate on code. Awesome Graphs enriches Bitbucket with graphs and reports, which let you visualize, track and analyze the activity in your projects.
Recently we’ve added new great features and would like to tell you how you can benefit from them. Keep reading if you are interested in:
- Viewing how the efforts of each developer are distributed among different projects
- Analyzing what developers may need to improve their work patterns and who’s doing a great job
- Learning what reviewers are most active and diligent
- Knowing the average time taken to resolve pull requests
Table of Contents
New perspective of developer activity
With Detailed view introduced in Contributions feature you can see the overview of developer activity from a new angle. It shows how the time and efforts of a developer were spread among different projects in the past month, quarter or year, and tells you what repositories and projects a person worked on and when. You can use this view to:
- See what projects a developer was involved in at different times
- Learn what projects a developer has been recently investing more time in
- Get data for retrospectives and insights about ways to improve development process, e.g. you can see if an engineer:
- had to switch between projects too much
- had gaps with no activity at all (maybe he or she was waiting for deliverables and couldn’t start their work in time)
- Analyze commits and pull requests a developer made in the past quarter to see if there are some work patterns that need to be changed
Code review analysis
New Contributions Report analyzes activity in pull requests (tasks, comments, needs work/approved/declined statuses). It helps you understand:
- What developers create high quality code and who might need to improve their approach to work. E.g. when an engineer has less tasks, comments and needs work flags in their pull requests, it suggests his work is approved as it is or with minor changes and he creates code of high quality.
- What reviewers are thorough when they review the work of developers. E.g. diligent reviewers come up with suggestions and improvements, so they have more tasks and comments than others.
- How the dynamics of code review changes over time. E.g. you can see if the number of pull requests with Needs work flags is getting bigger or smaller, if the number of tasks in pull requests is increasing or decreasing over time.
Average time taken to resolve pull requests
Another new report, Resolution Time Report, shows the average time taken to resolve pull requests. This is helpful to capture trends in resolution time. It displays resolution times of merged and declined pull requests separately. With this report you can:
- Notice spikes in resolution time and then dive in to see what went wrong
- See if an average resolution time is high for a long period of time – it can be a signal to look into your code review process and determine what causes delays
- Monitor how changes in your proccesses affect the speed of code review
What other reports do you need?
Awesome Graphs already has a wide range of graphs and reports that help you answer various questions about project development and the work of your team in Bitbucket. We are open to your feedback and appreciate hearing about what you need. So if you have a problem that you think Awesome Graphs can help you with, contact us – we actually listen.