Pull Requests Team Workload
No matter the size of your team, there’s always a decision to be made when it comes to decide who should review your pull request (PR). The main goal of the review process is to set quality standards and find bugs before hitting production. While in small teams you might tend to choose the tech lead, in bigger teams are policies or rules to choose several reviewers. Sometimes you might just accept the reviewer recommendations that the tool automatically provides.
And that’s fine. However, there are always the usual suspects, which are those developers who are always overwhelmed with tons of PRs.
This gadget displays the leaderboards in terms of number of pull requests pending to review. Those developers with more workload than the rest, who will beg you to check this gadget the next time you have to decide who should review your code.
Name your gadget meaningfully, so everyone knows at a glance what it is about and when to use it. Fill out the rest of the fields as applicable, namely:
The datasource to connect to Bitbucket Pipelines. Remember that you need the Dashboard Hub Connector for Bitbucket app, see Dashboard Hub Connector Apps if you don’t know what is that.
The repository (or repositories) where the pull requests are waiting to be reviewed.
Finally, indicate if you want to use the current settings for all the compatible gadgets in the dashboard. This option eases the pain of configuring one by one the rest of the gadgets with the same default configuration
We are working on our growing catalog of Dashboard Gadgets: KPIs and Metrics and Dashboard Integrations: Supported Products, but contact us you want us to expedite a specific one, visit our Help Center.
This gadget appears in the following dashboard: Scrum Software Team template. See