Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Technical Metrics is displayed for all the projects, and shows details for the following data sources:
Source Control dashboards show analytics for git commits based on a project's configuration:
The data on Source Control dashboards do not include commits by Bots and empty commits. By default, Bot commit is filtered, . For details, see Filter Data.
By default, Bot commit is filtered. To add/manage filters, see Add and Manage Data Filters.
The GitHub PR dashboards represent a set of metrics that shows pull request information of GitHub repositories of the project. Following are the various dashboards of GitHub PR:
By default, Bot commits are filtered. To apply more filters, see add and manage data filters.
Overview shows all the information about pull requests for a project.
Filter lets you filter the dashboard data by author name, organization name, repository name, and repository URL. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the total number of pull requests, submitters, and repositories of the project over time.
Most Used PR Labels shows a cluster of top 10 Pull request labels. Click a label to filter the project dashboard to view label related details. Click the cross mark next to a label in the Add Filter navigation bar to remove the filter.
Submitters Over Time shows a bar graph that represents the number of pull request submitters per day over time. Mouse over a color in the graph to see the total number of submitters that occurred on a date.
Pull Requests By Organization shows a doughnut chart that represents the total number of pull requests per organization over a time range. Mouse over a color (organization) in the chart to see the organization name, total number and percentage of pull requests.
PRs Created Over Time shows a periodic line graph that displays the number of Pull Requests created over time. Hover mouse over the graph to view the date and number of PRs created on the date.
Pull Requests By Submitters shows a table that lists submitter name, number of pull requests by the submitter, number of repositories the submitter submitted PRs to, number of merged, rejected and open PRs by the submitter, and average number of days taken to merge the submitter's PRs.
Pull Request by Organization shows a table that lists and lets you sort values by organization name, number of Pull Requests submitted by the organization over time, total number of submitters of the organization, and number of repositories to which the submitters of the organization have submitted PRs .
Pull Requests By Repositories shows a table that lists and lets you sort values by repository link, number of pull requests per repository, number of PR submitters for the repository, and average time taken in days to merge the PRs. You can select a repository to view details on GitHub.
Efficiency offers an overall view of understanding and optimizing project efficiency in closing GitHub Pull Requests.
Filter lets you filter the project data by organization name, author name, repository name, and repository URL. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows a cluster of
50th percentile of Time To Merge (Days): The number of days it took to merge 50 percent of the pull requests.
95th percentile of Time To Merge (Days): The number of days it took to merge 95 percent of the pull requests.
Merged PRs: Total number of pull requests merged.
Organizations: Total number of organizations whose submitters authored the merged pull requests.
Submitters: Total number of submitters whose pull requests were merged.
Repositories: Total number of repositories the merged pull requests belonged to.
50th percentile of Time To Close By Repo shows a cluster of top 10 repositories names for which it took most time to merge 50% of the pull requests.
Time to Merge shows a graph that displays number of Pull Requests that took certain amount of time to get merged. These time slots are divided into four categories, such as less than 1 day, 1 to 7 days, 7 to 30 days, and more than 30 days. Hover mouse over the graph to view number of of PRs along with the time taken to get merged.
Less than 1 day: The number of pull requests merged in less than one day.
1 to 7 days: The number of pull requests merged in more than one day but less than seven days.
7 to 30 days: The number of pull requests merged in more than seven days but less than thirty days.
More than 30 days: The number of pull requests merged in more than thirty days.
Repositories shows a table that lists repositories, total number of PRs merged along with the time it took for 50% and 95% of the PRs to get merged per repository. Click a repository to navigate to GitHub to view details.
Timing shows information about open and closed pull requests in time. The dashboard focuses on how long pull requests remain open. Statistical information provides closing times and also tables with the latest and the oldest pull requests.
Filter lets you filter the dashboard data by author name, organization name, repository name, and repository URL. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the total number of Pull Requests, Submitters, Assignees, Average number of days the PRs are in open state, and average number of days taken to merge Pull Requests.
Pull Requests by Organization shows a doughnut chart that represents the total number and percentage of pull requests submitted by organizations. Mouse over a color in the chart to see the total number and percentage of pull requests submitted by the organization.
Median Time to Merge (Days) shows a line graph that represents number of days it took for 50% of open pull requests (out of all PRs created on a date) to get merged . Mouse over a color in the graph to see the number.
Submitters shows line graphs that represent the number of submitters and organizations who raised pull request over time. Mouse over a color in the graph to view the date and number of organizations and submitters that created PRs.
Median Time To First Review shows a line graph that displays the number days it takes for 50% of the pull request to get their first review over time.
Median Time To First Approval shows a line graph that displays the number days it takes for 50% of the pull request to get their first approval over time.
Submitters shows a table that lists name of submitters, number of pull requests raised by the submitter, number of repositories the submitter worked upon, total number pull requests raised by the submitter by status, such as merged, rejected and open states, and average time in days it takes to merge the pull request submitted by the submitter.
Organizations shows a table that lists organization name, total number of pull requests submitted by the organization along with number of PRs by status, such as merged, rejected and open state, and average time taken in days to merge the PRs per organization.
Repositories shows a table that lists and let you sort values by repositories, number of pull requests along with number of PRs by status, such as merged, rejected and open state, submitters, and average time taken to merge the PRs per repository.
Backlog focuses on open pull requests (data is retrieved at the moment of dashboard creation), their accumulated time, associated organizations and submitters.
Filter lets you filter the dashboard data by author name, organization name, repository name and URL. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows total number of pull requests in open state, total number of repositories having pull requests in open state, and average number of days pull requests have been in open state.
Pull Request Backlog Percentage By Organizations shows a pie chart that displays the number and percentage of pull requests in open state by organization. Mouse over a color in the chart to view details.
Backlog (Open Pull Requests) shows a table that provides a summary of oldest PRs that are in open states, and are waiting to be closed. It lists PR URLs for the project. For each PR, the table shows the summary, date and time the PR was created, and how long (in days) the PR have been in open state. Click a URL to go to the changeset in the project.
Backlog shows a line graph that represents the number of pull requests that are open on a particular day. Mouse over a color in the graph to see the total number of pull requests on a date.
Backlog By Submitters shows a table that lists submitter name, number of pull requests raised by the submitter, number of repositories the submitter worked upon, and average time in days the pull requests are in open state for a submitter.
Backlog By Organizations shows a table that lists organization name, number of pull requests raised by the organization, number of submitters from the organization, number of repositories the submitters of the organization worked upon, and average number of days the pull requests raised by the organization are in open state.
Backlog By Repositories shows a table that lists repository URL, number of pull requests raised, number of submitters, and average number of days the pull requests are in open state per repository.
Reviews provides an overall analysis of reviewed pull requests, approved ones, dismissals, average time to first review, approve, and so on along with the associated organizations and reviewers.
Filter lets you filter the dashboard data by reviewer name, organization name, repository name and URL. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the following details:
Submitted: Total number of PRs created (submitted) and reviewed across all monitored repositories.
Reviewers: Total number of unique PR reviewers across all monitored repositories.
Approvals: Total number of approvals received on all submitted PRs.
Changes Requested: Total number of 'Request Changes' received on all submitted PRs.
Review Comments: Total number of Comments received on all submitted PRs.
Dismissed: Total number of PR reviews being dismissed.
Avg. Time to First Review: The average time it took to get the first review on the PR across all submitted PRS.
Repos By Review Activity shows a cluster of top 10 repositories on which most review activity happened. Click a repo to view dashboard data specific to the repository.
PR Review States shows a doughnut chart that displays the number and percentage of pull request reviews by state, such as commented, approved, changes requested, and dismissed. Mouse over a color to view details.
Median Time To First Review shows a line graph that displays the 50th percentile of days it takes for a pull request to get a review in a given timeframe. Mouse over the graph to view details.
Median Time To First Approval shows a line graph that displays the 50th percentile of days it takes for a pull request to get an approval in a given timeframe. Mouse over the graph to view details.
PRs Merged Without Approval shows a line graph that shows the number of pull requests merged without approval on a particular day. Mouse over the graph to view details.
Repository PR Review Summary shows a table that lists repository URL, number of submitters, reviewers, review comments received per repository, and number of approved, changes requested, and dismissed PRs per repository over time.
Organization PR Review Summary shows a table that lists organization name, total number of pull requests raised by the organization, number of reviewers, review comments received for PRs raised by the organization, and number of approved, changes requested, and dismissed PRs per organization over time.
Reviewer Activity shows a table that lists reviewer names, total number of activity by the reviewer, number of approved, changes requested, review comments and dismissed PRs per reviewer over time. Total Activity is the sum of all activities done by the reviewer, such as how many PRs they approved, provided comments for, dismissed, and requested changes.
Latest PRs Review Activity shows a table that lists GitHub pull request link, date on which the PR is created, and if the PR is approved or dismissed, or any number of review comments and changes requested for the PR. Numbers as one and zero are used to indicate true or false for approved and dismissed PRs.
Click to copy the path of respective dashboards.
Issue Management dashboards show overview, backlog, effort, and timing analytics of the following issue tracking platforms:
By default, Bot Commits are filtered, however, you can include the filter values by navigating to the filter section of dashboard. For details, see Add and Manage Data Filters.
Following are the various dashboards of GitHub Issues:
Overview shows information about issues in project repositories and who submitted the issues and when. For each commit, information about the corresponding organization is also provided.
Filter lets you filter the dashboard data by author name, organization name, and repository. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the total number of issues, submitters, and repositories for the project.
Issues by Organization Over Time shows a stacked bar graph that represents the number of issues created by organizations per day.
Issues by Status Over Time shows a stacked bar graph that represents the number of open and closed issues over time.
Issues Percentage by Organization shows a doughnut chart that represents the total number of issues created by each organization over time. Mouse over a color (organization) in the chart to see the organization name, total number and percentage of issues.
Issue Submitters Over Time shows a bar graph that shows the number of submitters of issues per day over time.
Issues By Submitters shows a table that lists submitter name, total number of issues raised by the submitter, number of issues that are in open and closed state out of the total issues, number of repositories the submitter worked upon, and average number of days it took to close the issues raised by the submitter.
Issues By Organizations shows a table that organization name, total number of issues raised by the organization, number of issues in open and closed states, number of submitters, and average number of days the it took to close the issues raised by the organization.
Issues By Repositories shows a table that lists project's repository links, total number of issues, number of issues in open and closed states for the repository, number of submitters, and average number of days it took to close the issues. You can select a repository to view its details in GitHub.
Efficiency offers an overall view of understanding and optimizing project efficiency in closing GitHub issues.
Filter lets you filter the project data by organization name, author name, repository name, and repository URL. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows a cluster of
Total number of closed issues
Number of submitters whose issues are closed
Number organizations that helped in closing the issues
Repositories of the project to which the closed issues belong to
Number of days it took to close 50 percentage of the issues, and
Number of days it took to close 95 percentage of the issues over time
50th percentile of Time To Close By Repo shows a cluster of top 10 repositories names for which it took most time to close 50% of the issues.
Time to Close shows line graphs that represent number of issues that took certain amount of time to get closed. These time slots are divided into four categories, such as less than 1 day, 1 to 7 days, 7 to 30 days, and more than 30 days. Hover mouse over the graph to view number of of PRs along with the time taken to get merged.
Less than 1 day: The number of pull requests merged in less than one day.
1 to 7 days: The number of pull requests merged in more than one day but less than seven days.
7 to 30 days: The number of pull requests merged in more than seven days but less than thirty days.
More than 30 days: The number of pull requests merged in more than thirty days.
Repositories shows a table that lists repository link, time it took for 50% and 95% of the issues to get closed per repository. Click a repository to navigate to GitHub to view details.
Timing shows information about open and closed issues in time. The dashboard focuses on how long Issues remain open. Statistical information provides closing times and also tables with the latest and the oldest Issues.
Filter lets you filter the dashboard data by author name, organization name, and repository. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the total number of issues, submitters, assignees, average number of days issues in open state have been in open, and average number of days it takes to close issues.
Issues By Status shows a doughnut chart that represents the total number of issues over time by status: closed or open. Mouse over a color in the graph to see the status, the total number of issue for the status, and the date.
Issues By Organization shows doughnut chart that represents the total number of issues (closed and open) by an organization over time. Mouse over a color in the chart to see organization name, total number of issue for the organization, and date.
Median Time Open (Days) shows a graph that represents number of days for which 50% of issues, out of total issues that are created on a particular day, are open.
Submitters Over Time shows line graphs that represent the total number of individual submitters and submitters per organizations over time in the project. Mouse over a color in the graph to see the status, total number of submitters and the date.
Submitters shows a table of submitters and their corresponding number of Issues, Repositories, and Avg. Open Days.
Organizations shows a table that lists organization name, total number of submitters from the organization, number of open and closed issues, and average number of days it took to close the issues per organization.
Repositories shows a table listing repositories, total number of issues per repository along with the number of open and closed issues , and average number of days it took to close the issues per repository.
Backlog focuses on open issues, their accumulated time, and associated organization.
Filter lets you filter the dashboard data by author name, organization name, repository name and URL. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows total number of issues in open state, total number of repositories with issues in open state, and average number of days issues have been in open state.
Backlog shows a line graph that represents the number of issues that are open on a particular day. Mouse over a color in the graph to see the total number of issues on a date.
Backlog (Open Issues) shows a table that lists summary, URL, date on which the issue was open, and average number of days the issue was in open state. Click the URL to view details.
Open Issues Statistics Summary shows the total number of Open Issues, Accumulated time in days for Open issues, and Average Time Open per Issue.
Percentage of Issues Opened By Organizations shows a doughnut chart that represents the total number of issues opened per organization. Mouse over a color in the chart to see the total number and percentage of issues raised by an organization.
Issues In Open By Submitters shows a table that lists name of the submitter, total number of issues raised by the submitter, number of repositories the submitter worked upon, and average number of days the issues were in open state per submitter.
Issues In Open By Organization shows a table that lists name of the organization, total number of issues submitted by the organization, number of submitters from the organization, and average number of days the issues were in open state per organization.
Click to copy the path of respective dashboards.
By default, Bots and Changesets Only are filtered. Dashboard shows data only for number of changesets, not for comments, approvals, and other values. Empty changesets— Changesets that have value as zero— are also filtered. To add/manage filters, see Add and Manage Data Filters.
The Gerrit Changesets dashboards represent a set of metrics that shows detailed information about changesets and patchsets per changeset. Following are the various dashboards of Gerrit data source:
By default, Bots and Changesets Only filters are applied. To apply more filters, see add and manage data filters.
Overview shows visualizations that provide information about changeset statuses, submitters, and organizations. Changeset information per organization and repository is also shown.
Filter lets you filter the dashboard data by author name, organization name, and repository. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows total number of changeset submitters, repositories the changesets belong to, new changesets, merged changesets, and total number of abandoned changesets.
Changeset Percentage By Status shows a doughnut chart that represents the total number of changesets in the project by status: MERGED, ABANDONED, NEW, DRAFT. Mouse over a color in the chart to see the status, total number, and percentage of changesets by status.
Changeset Percentage By Organization shows a doughnut chart that represents the total number and percentage of changesets submitted by an organization over time. Mouse over a color in the chart to see details.
Changesets By Status shows stacked line graphs that represent the increase or decrease in the number of changesets by status—MERGED, ABANDONED, NEW, DRAFT— that were started per day. Mouse over a color in the graph to see the status along with its number, and the date the changesets was started.
Changeset Submitters shows stacked line graphs that represent increase or decrease in the total number of changeset submitters over time along with the number of organizations the submitters belong to. Mouse over a color in the graph to see the numbers for a date.
Patchsets per Changeset shows stacked line graphs that represent the 50th, 75th, and 95th percentile of patchsets created per changeset in a given timeframe. Mouse over a color in the graph to see number of patchsets.
Changesets By Organizations shows a stacked bar graph that represents the number of changesets submitted by an organization over time. Mouse over a color in the graph to see details.
Submitters shows a table that lists name of the submitters, total number of changesets submitted by the submitter, total number of new, merged, and abandoned changesets per submitter. It also lists average number of patchsets over total number of changesets submitted by a submitter over time.
Organizations shows a table that lists organization names, number of submitters from the organization, total number of changesets submitted by the organization's submitters, number of changesets in different stages, such as new, merged, and abandoned, and average number of patchsets over total number of changesets submitted by an organization over time.
Repositories shows a table that lists name of the repository, total number of changesets submitted to the repository, number of contributors who submitted changesets to the repository, number of changesets in different stages, such as new, merged, and abandoned, and average number of patchsets over total number of changesets submitted by to the repository over time.
Latest Changeset Activity shows a table that lists changeset URL, changeset submitter's name, affiliated organization of the changeset submitter, status of the changeset, number of patchsets created for the changeset, and date and time when the changeset was updated.
Efficiency offers an overall view of understanding and optimizing project efficiency in closing/merging Gerrit Changesets.
Filter lets you filter the project data by organization name, author name, and repository name. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows a cluster of
50th percentile of Time To Merge (Days): The number of days it took to merge 50 percent of the changesets.
95th percentile of Time To Merge (Days): The number of days it took to merge 95 percent of the changesets.
Merged Changesets: Total number of changesets merged over time.
Organizations: Total number of organizations whose submitters authored the merged changesets.
Submitters: Total number of submitters whose changesets were merged.
Repositories: Total number of repositories the merged changesets belonged to.
50th Percentile of Time To Merge By Repo shows a cloud of top 10 repositories for which it took the most time for 50% of the changesets to get merged. Click a repository to filter the dashboard data to view metrics related to the repository.
Time to Merge shows line graphs that represent number of changesets that took certain amount of time to get merged. These time slots are divided into four categories, such as less than 1 day, 1 to 7 days, 7 to 30 days, and more than 30 days. Hover mouse over the graph to view number of of PRs along with the time taken to get merged.
Less than 1 day: The number of changesets merged in less than one day.
1 to 7 days: The number of changesets merged in more than one day but less than seven days.
7 to 30 days: The number of changesets merged in more than seven days but less than thirty days.
More than 30 days: The number of changesets merged in more than thirty days.
Repositories shows a table that lists repositories, total number of merged changesets along with the time it took for 50% and 95% of the changesets to get merged per repository. Click a repository to navigate to GitHub to view details.
Timing shows information about open and closed changesets over time. The dashboard focuses on how long changesets remain open. Statistical information provides closing times and also tables with the latest and the oldest changesets.
Filter lets you filter the dashboard data by repository, author who submitted changesets, and author who approved the changesets. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the total number of changeset submitters, number of new, merged, and abandoned changesets, and average number of days the changesets are open, and average number of days it took for the changesets to be merged.
Changesets By Organization shows a doughnut chart that represent number and percentage of changesets submitted by an organization over a time period. Mouse over a color to view details related to an organization.
Median Time To Merge (Days) shows line graphs that represent the increase or decrease in time it takes for 50 percent of the changesets to be merged.
Submitters shows line graphs that represent the increase or decrease in the number of changeset submitters and their affiliated organizations over time.
Median Time To First Review shows line graphs that represent the 50th percentile of days it takes for a changeset to get reviewed in a given timeframe.
Organizations shows a table that lists organization name, number of submitters from the organization, number changesets submitted by the organization's submitters, number of changesets in different stages, such as new, merged and abandoned, average number of patchsets submitted per total changesets, and average number of days it took to merge the changesets for an organization.
Submitters shows a table that lists name of the submitters, total number of changesets submitted by the submitter, number of changesets in different stages, such as new, merged and abandoned, average number of patchsets submitted by the submitter over time, and average number of days it took to merge the changesets submitted by a submitter.
Repositories shows a table that lists repository name, total number of changesets submitted to the repository, total number of submitters, number of changesets (submitted to the repository) in different stages, such as new, merged and abandoned , average number of patchsets per changesets over time, and average number of days it took to merge the changesets for a repository.
Backlog focuses on open changesets (data is retrieved at the moment of dashboard creation), their accumulated time, and associated organizations.
Filter lets you filter the dashboard data by author name, organization name, and repository. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows total number of new changesets that are in open state, number of repositories where the new changesets are submitted, and are in open state, and average number of days changesets have been in open state.
Changeset Backlog Percentage By Organization shows a doughnut chart that displays number and percentage of changesets created by on organization over time. Mouse over a color to view details.
Backlog (New Changesets) shows a table that provides a summary of oldest changesets that are in open states, and are waiting to be closed. It lists changeset URLs for the project. For each changeset, the table shows the summary, the submitter name, the date and time the changeset was created, and how long (in days) the changeset have been in open state. Click a URL to go to the changeset in the project.
Backlog shows line graphs that displays the number of new changesets created over time.
Backlog By Submitters shows a table that provides summary of new changesets created by individual submitters. It lists submitter's names, number of changesets and average number of patchsets created by the submitter, and average number of days the changesets have been in open state.
Backlog By Organizations shows a table that provides summary of new changesets created by organizations. It lists organizations' names, number of submitters of the organization, number of changesets and average number of patchsets created by the organizations' submitters, and average number of days the changesets have been in open state.
Backlog By Repositories shows a table that provides summary of new changesets submitted to repositories. It lists repository names, number of submitters to the repository, number of changesets and average number of patchsets submitted to the repository, and average number of days the changesets have been in open state for a repository.
Approvals shows statistics about changesets that are approved. The dashboard shows reviewers, repository names, numbers of respective data, and so on.
Filter lets you filter the dashboard data by repository, author who submitted changesets and author who approved changesets. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows
Approvals: Sum of all approvals given on all the changesets
Changesets Approved: Number of changesets that were given an approval
Approvers: The number of reviewers that approved the changesets
Approvals By Organization shows a doughnut chart that represents the number and percentage of changesets that are approved by the authors of the organization. Mouse over a color in the chart to view details.
Reviewers Over Time shows a graph that represents total number of reviewers who reviewed changesets for the project over time.
Approvals Over Time shows graphs that represent number of changesets in different states over time. Mouse over a color to view details.
Activity by Repository shows a table that lists name of the repository, total number of changesets, patchsets, and approved changesets per repository.
Approvals Done by Reviewer shows a table that lists reviewer name, number of changes approved by the reviewer, and number of code review ratings (-2, -1, 1, 2) given by the reviewer for the repository over time.
Approvals by Reviewer Organization shows a table that provides summary of organizations that approved changesets. It lists name of the organization that approved changesets, number of changesets approved by the organization, and number of code review ratings (-2, -1, 1, 2) given by the reviewers of the organization over time.
Approvals Received shows a table that provides summary of changeset submitters who received maximum number of approvals. It lists name of the changeset submitter, number of approvals received by the submitter, and number of code review ratings (-2, -1, 1, 2) received by the submitter over time.
Reviews shows metrics about reviewed changesets. The dashboard shows reviewers, repository names, numbers of respective data, and so on.
Filter lets you filter the dashboard data by reviewer name, organization name, and repository. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the total number of changesets, total number of individuals who reviewed changesets, total number approved changesets, total number of review comments received for the submitted changesets, and average time in days it took to review the first changeset.
Repos By Review Activity shows a cloud of top 10 repositories where maximum number of review activities happened. Click a repository to view the dashboard data specific to the repository.
Review Types shows a doughnut chart that represents the total number and percentage of changesets in the project by review status: Comment, Approval, Patchset, and Changeset. Mouse over a color in the chart to see the status, total number, and percentage of changesets by review status.
Median Time to First Review shows a graph that displays 50th percentile of days it takes for a changeset to get a review in a given timeframe_._ Mouse over a color in the graph to see the data.
Changesets Merged Without Approval shows graph that displays number of changesets that are merged without going through a approval process, over a period of time.
Repository Changeset Review Summary shows a table that displays review activity per repository, and lets you sort values by repository name, number of submitters and reviewers per repository, total number of changesets submitted to the repository, number review comments and approvals received for changesets per repository.
Organization Changeset Review Summary shows a table that displays review activities per organization, and lets you sort values by organization name, number of submitters and reviewers of an organization, total number of changesets submitted by an organization, number review comments and approvals given by an organization's submitters over time.
Reviewer Activity shows a table that displays activities by top reviewers. It list reviewer name, reviewer's organization name, number of changesets and patchsets reviewed by the reviewer, number of review comments given, number of changesets approved by the reviewer along with the total number of activities done by the reviewer.
Click to copy the path of respective dashboards.
CI/CD dashboards show continuous integration, build and job analytics for the project. For details, see:
The DockerHub dashboard is available from Registry **** drop-down list, and represents a set of metrics that provide information about DockerHub container images.
Overview shows high-level information about docker images.
Filter lets you filter the dashboard data by docker image. Select values from the drop-down list, and click Apply changes to filter the dashboard as per selection.
DockerHub shows the total number of Docker Images, 50th percentile of Median Stars by Image, and 50th percentile of Median Pulls by Image.
Top Image Pulls shows a doughnut chart that represents top docker images. Mouse over a color in the chart to view details, such as docker image name, number, and its percentage.
Total Stars shows a table that represents total number of stars per calendar period. Mouse over to view details for a calendar date.
Total Pulls shows a table that represents total number of pulls per calendar period. Mouse over to view details for a calendar date.
Pull Trends shows a comparison of pull counts and trends for a calendar period.
Images shows a table that lets you sort values by Docker Image, Stars, and Pulls.
By default, Bot Commits are filtered, however, you can include the filter value by navigating to the filter section of dashboard. For details, see Add and Manage Data Filters.
The Bugzilla dashboard is available from the Issue Management drop-down list, and represents the following dashboards:
Overview shows information about issues and submitters in Bugzilla organizations.
Filter lets you filter the dashboard data by submitter name, organization name, and project. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Issues shows the total number of Issues, Submitters, and Products.
Issues by Status Over Time shows a stacked bar graph that represents the number of issues by status per day over time such as: RESOLVED, CONFIRMED, IN_PROGRESS, VERIFIED, UNCONFIRMED. Mouse over a color in the graph to see the total number of issues by status that occurred on a date.
Submitters by Organization shows a doughnut chart that represents the total number of submitters in the project by organization. Mouse over a color in the chart to see the total number of submitters for the organization, and their percentage of the project's organization.
Projects shows a table that lets you sort values by Organizations, Issues, Submitters, Assignees, Avg. Time to close (days) and Avg. Updates.
Submitters Over Time shows a bar graph that represents the number of submitters per day over time. Mouse over a color in the graph to see the total number of submitters that occurred on a date.
Submitters shows a table that lets you sort values by Submitter, Issues, Products, and Avg. Open Days.
Issues by Organization Over Time shows a stacked bar graph that represents the number of issues by organization per day over time. Mouse over a color in the graph to see the total number of issues that occurred on a date for the organization.
Organizations shows a table that lets you sort values by organization name, number of issues, submitters, assignees, average time to close (days) issues, and average updates per product.
Backlog focuses on open issues, their accumulated time, and associated organizations.
Open Issues Statistics shows total number of open issues, accumulated time in days for all open issues, and average time in days an issue is open.
Issues waiting to be closed shows a stacked bar graph that represents number of issues (that are not closed) per day by status: New, Unconfirmed, Assigned, and so on. These statuses are color coded. Mouse over a color in the graph to see the total number of issues by status that occurred on a date.
Backlog shows a table that lets you sort values by title, URL, number of comments, updates, days of open, and date of open for an issue backlog.
Accumulated Time (days): Issues waiting to be closed shows a bar graph that represents cumulative number of days for which individual issues were open, on a date. Mouse over a color in the graph to see the data.
Assignee Organizations shows a doughnut chart that represents the assigned organizations that have open issues to be closed. Mouse over a color in the chart to see the total number of assignees for the organization, and their percentage.
Backlog Submitters shows a table that lets you sort values by submitter name, number of issues, average time in days the issue was open for the submitter, and number of projects the submitter is associated with.
Projects shows a table that lets you sort values by project name, number of open issues, and average time in days the issues are open.
bugzilla_openissues_per_organization shows a table that lets you sort values by organization name, number of open issues, and average time in days the issues are open for an organization.
Timing shows information about open and closed issues in time and lets you focus on how long Issues remain open. Statistical information shows the 50th percentile of median time open in days. The number indicates the median number of days that issues were open. This number indicates that 50 percent of the issues were open longer than the total number and 50 percent of the issues were below the total number. A 50th percentile is the same as a median.
Summary shows the total number of Issues, Submitters, Assignees, 50th percentile of Median Open Days.
Median Open Time (days) shows a stacked bar graph that represents number of days for which the median or 50th percentile of total issues that were created per day over time, are open. Mouse over a color in the graph to see the median number of days issues were open on a date.
80 percent Open Time (days) shows a stacked bar graph that represents number of days for which the 80th percentile of total number of issues that were created per day, are open. Mouse over a color in the graph to see the 80th percentile number of days issues were open on a date.
Issues shows a stacked bar graph that represents the total number of issues over time in the project by status: closed, open, resolved, in progress, and so on. Mouse over a color in the graph to see the status, the total number of issue for the status, and the date.
Issue By Status shows a doughnut chart that represents the total number of issues in the project by status: closed, open, resolved, in progress, and so on. Statuses are color code. Mouse over a color in the chart to see the status, total number of issues for the status, and the percentage of that status.
Issues Assigned by Organization shows a doughnut chart that represents the total number of issues assigned by an organization. Mouse over a color in the chart to see the number of issues, and their percentage for an organization.
Issues By Resolution shows a doughnut chart that represents the number and percentage of issues by resolution status—Fixed, Duplicate, Invalid, Notabug. Mouse over a color to see the data.
Issues By Severity shows a doughnut chart that represents the number and percentage of issues by severity status—normal, enhancement, critical, major. Mouse over a color to see the data.
Submitters shows
a bar graph that represents the total number of submitters over time for the project. Mouse over a color in the graph to see total number of submitters for a date.
a table of submitters and their corresponding number of Issues, products, and Avg. Open Days.
Organizations shows a table that lets you sort values by organization name, number of open issues, submitters, assignees, and verage time in days issues are open for an organization.
Projects shows a table that lets you sort values by project name, number of open issues, submitters, assignees, products, and verage time in days issues are open for an organization.
Products shows a table that lets you sort values by product name, number of open issues, submitters, assignees, and average time in days issues are open.
Latest Issues shows a table listing issues by Title, Product, Submitter, URL, Id, and Created on. The default sort is by most recently created issue.
By default, Bot Commits and Issues Only are filtered. Dashboard shows data only for number of issues, not for comments, and other values. You can include these filter values by navigating to the filter section of dashboard. For details, see Add and Manage Data Filters.
The Jira dashboards under Issue Management represents a set of metrics that shows an analysis of Jira issues . Following are the various dashboards of Jira dashboard:
Overview shows information about issues in repositories and who submitted the issues and when. For each commit, information about the corresponding organization is also provided.
Filter lets you filter the dashboard data by submitter name, organization name, and project. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows total number of issues, submitters , and projects.
Backlog shows a line graph shows the total number of issues in open state over time.
Issues by Status shows a stacked bar graph that represents the number of issues by status per day over time. Issue statuses are color code. Mouse over a color in the graph to see the total number of issues by status that occurred on a date.
Issues Assigned To Organization shows a stacked bar graph that represents the number of issues assigned to an organization per day over time. Organizations are color code. Mouse over a color in the graph to see the total number of issues assigned to the organization on a date.
Issues Submitted By Organization shows a stacked bar graph that represents the number of issues submitted by an organization per day over time. Organizations are color code. Mouse over a color in the graph to see the total number of issues submitted by the organization on a date.
Submitters hows a bar graph that represents the number of submitters per day over time. Mouse over a color in the graph to see the total number of submitters and the date.
Submitters by Organization shows a doughnut chart that represents the organizations that submitted issues (not unique issues; it includes activities on issues, such as comments, approvals, and so on) in the project. Mouse over a color in the chart to see the total number of submitters for the organization, and their percentage of the project's organization.
Assignees by Organization shows a doughnut chart that represents the organizations that are assigned with the issues (not unique issues; it includes activities on issues, such as comments, approvals, and so on) in the project. Mouse over a color in the chart to see the total number of assignees for the organization, and their percentage of the project's organization.
Assignees shows:
a stacked bar graph that represents total number of assignees for a calendar period. Mouse over a color in the graph to see total number of assignees for a date.
a table that lets you sort values by assignees names, number of issues, projects, reporters, and average time in days the issues were open before they were closed.
Submitters shows a table that lets you sort values by submitters names, number of issues, projects, assignees, and average number of days the issues were open per submitter over time .
Issues By Projects shows a table that lets you sort values by project name, number of issues, submitters, assignees, average number of watchers, and average time in days to close the issues over time.
Issues By Organization shows a table that lets you sort values by organization name, number of issues, submitters, assignees, average number of watchers, and average time in days to close the issues over time.
Effort shows data about authors and assignees, and their effort in hours per project and organization.
Filter lets you filter the dashboard data by submitter name, organization name, and project. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the total number of Items, Authors, Assignees, Total Hours Estimated, Total Hours Remaining, and Total Hours Logged for the project.
Assigned Organizations shows a doughnut chart that represents the total number of assignees per organization. Mouse over a color in the chart to see the total number of assignees per organization, and the percentage of assignees for that organization out of the total assignees.
Estimated by Repository shows a doughnut chart that represents the total number of estimated hours per repository. Mouse over a color in the chart to see the total number of estimated hours per repository, and the percentage of estimated hours for that repository out of the total hours.
Logged by Repository shows a doughnut chart that represents the total number of logged hours per repository. Mouse over a color in the chart to see the total number of logged hours per repository, and the percentage of logged hours for that repository out of the total hours.
Effort (hours) shows a stacked bar graph that represents the effort expressed in the number of estimated, remaining, and logged hours over time. Mouse over a color in the graph to see the total number of hours: Estimated, Remaining, or Logged for a date.
Effort (hours, cumulative sum) shows a multi-line graph that represents the effort expressed in the number of time estimated, time remaining and time logged hours over time. Mouse over a color in the graph to see a vertical line that represents the time and date, and shows the total number of hours: Estimated, Remaining, or Logged for that date.
Averages and Medians shows a table that lets you sort values by Avg. Hours Estimated, Avg. Hours Remaining, Avg. Hours Logged, 50th percentile of Median Hours Estimated, 50th percentile of Median Hours Remaining, and 50th percentile of Median Hours Logged. The 50th percentile number indicates the median number of hours estimated or remaining. A 50th percentile is the same as a median.
Remaining by Repository shows a doughnut chart that represents the total number of remaining hours per repository. Mouse over a color in the chart to see the total number of remaining hours per repository, and the percentage of remaining hours for that repository out of the total hours.
Effort by Author and Assignee (hours) shows a table that lets you sort values by authors, assignees, URL, and estimated, remaining, and logged hours.
Effort by Organization (hours) shows a table that lets you sort values by organization name, number of issues, submitters, assignees, average number of watchers, Avg. Estimated Time (hours), Avg. Logged Time (hours), and Avg. Remaining Time (hours) per organization,.
Effort by Repository (hours) shows a table that lets you sort values by Repository, Issues, Submitters, Assignees, Avg. Num. Watchers, Avg. Estimated Time (hours), Avg. Logged Time (hours), and Avg. Remaining Time (hours).
Timing shows information about open and closed issues in time and lets you focus on how long Issues remain open. Statistical information shows the 50th percentile of median time open in days. The number indicates the median number of days that issues were open. This number indicates that 50 percent of the issues were open longer than that number and 50 percent of the issues were below that number. A 50th percentile is the same as a median.
Filter lets you filter the dashboard data by submitter name, organization name, and project. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the total number of Issues, Submitters, Assignees, 50th percentile of Median Open Days, and Avg. Open Days.
Issues Open in Median shows a bar graph that represents number of days for which the median number of total issues that were created per day over time, are open. Mouse over a color in the graph to see the median number of days issues were open on a date.
Issues Open (best 80 percent of them) shows a bar graph that represents number of days for which the 80th percentile of total number of issues that were created per day over time, are open. Mouse over a color in the graph to see the 80th percentile number of days issues were open on a date.
Issue Count By Status shows a doughnut chart that represents the total number of issues in the project by status: closed, open, to do, and so on. Statuses are color code. Mouse over a color in the chart to see the status, total number of issues for the status, and the percentage of the project's issues for that status.
Organizations shows a table that lets you sort values by organization name, number of issues, submitters, assignees, 50th percentile of Median Time Open Days, and 50th percentile of Median Changes per organization over time.
Projects shows a table that lets you sort values by project name, number of issues, submitters, assignees, 50th percentile of Median Time Open Days, and 50th percentile of Median Changes per project over time.
Issues shows a table that lets you sort values by Summary, Submitter, Status, Project, +Info, Open Date, and Open Days.
Backlog focuses on open issues, their accumulated time, and associated organization.
Filter lets you filter the dashboard data by submitter name, organization name, and project. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the total number of open issues, accumulated time in days while issues were open, and the average time in days per open issue over time.
Open Issues By Projects shows a table that lets you sort values by project name, number of issues and average time in days the issue were open over time.
Accumulated Time (days): Issues waiting to be closed shows a bar graph that represents cumulative number of days for which individual issues were open, on a date. Mouse over a color in the graph to see the data.
Issues waiting to be closed shows a stacked bar graph that represents number of issues (that are not closed) per day by status: Open, In Progress, To Do, and so on. These statuses are color coded. Mouse over a color in the graph to see the total number of issues by status that occurred on a date.
Issues In Backlog By Organizations shows a table that lets you sort values by organization name, number of issues, average time in days the issues were open per organization over time, and average number of watchers for issues over time.
Backlog Assignees By Organizations shows a doughnut chart that represents the assigned organizations that have open issues to be closed. Mouse over a color in the chart to see the total number of assignees for the organization, and their percentage.
Issues Submitters shows a table that lets you sort values by submitter name, number of issues, average time in days the issue was open for the submitter, and number of projects the submitter is associated with.
Issue Backlog Summary shows a table that lets you sort values by title, Info, repository, submitter, and total number of days the issue backlog was open. The default sort is by the greatest number of open days.
Click to copy the path of respective dashboards.
Click to copy the path of respective dashboards.
Registry shows metrics of container images.
The CircleCI dashboards under CI/CD drop-down list represents a set of metrics that show overview analysis of CircleCI build system data. Following are the various dashboards of CircleCI:
Overview shows total number of pipelines, workflows, and jobs for the project.
Job status percentage shows a doughnut chart that displays build jobs by status: success, failed and cancelled. Mouse over a color to view number and percentage of build jobs.
Workflow status percentage shows a doughnut chart that displays workflows of build jobs by status: success, failed, cancelled, and other. Other includes statuses such as running, not run, on hold, and so on. Mouse over a color to view number and percentage of workflows.
Job status trend shows line graphs that display total number of jobs per status on a timely basis. Mouse over the graph to view numbers.
Workflow duration trend shows line graphs that display minimum and maximum time (in minutes) taken to complete a workflow. It also displays the average time (in minutes) taken by 50% of the total number of workflows to be completed.
Workflow Duration (minutes) 95th Percentile shows a bar graph that displays time taken in minutes to complete 95% of total build jobs created per day.
Workflow status by author shows a table that lists name of authors, total number of workflows (by status) created by the author: success, failed, cancelled, and approved.
Workflow status by organization shows a table that lists name of organizations the authors belong to, total number of workflows (by status) created by the authors of the organization: success, failed, and cancelled.
Workflow status by origin repository shows a table that lists origin repositories where the build job is created, target repository, number of build jobs by status: success, failed, and cancelled.
Job run count shows table that lists the job number, related project name, and number of times the job was run to complete the workflow.
Jobs Overview shows total number of build jobs over time along with how many jobs are success, failed, and cancelled over time.
Job Status shows a doughnut chart that displays number and percentage of build jobs over time. Mouse over a color to view details.
Job Status on a time series shows a colored bar graph that displays timely total count of jobs along with the how many job numbers are success, failed, and cancelled over time.
Jobs status trend shows line graphs that represent gradual increase or decrease of the build jobs by status, such as how many jobs are success, failed or cancelled over time. Mouse over a point in the graph to view details.
Job duration trend shows line graphs that represent gradual increase or decrease in maximum and minimum time taken in minutes to complete the build jobs. It also shows average time taken in minutes to complete 50% of the total jobs created over time. Mouse over a point in the graph to view details.
Job duration-Max, Median and Min shows a colored bar graph that displays maximum and minimum time taken in minutes to complete the build jobs created over time. It also shows average time taken in minutes to complete 50% of the total jobs created over time. Mouse over a color in the graph to view details.
Job executor type shows a doughnut chart that displays number and percentage of jobs executed using a particular containerization technology, such as Docker. Mouse over a color to view details.
Job executor instance size shows a doughnut chart that displays number and percentage of completed jobs by size, such as large, medium, xlarge, and so on.
Workflow Overview shows total number of workflows over time along with how many workflows are success, failed, and cancelled over time.
Workflow duration trend shows line graphs that represent gradual increase or decrease in maximum and minimum time taken in minutes to complete the workflows. It also shows average time taken in minutes to complete 50% of the total workflows created over time. Mouse over a point in the graph to view details.
Workflow Status on a time series shows a colored bar graph that displays timely total count of workflows along with how many workflows are success, failed, and cancelled over time.
Workflow status by orgs shows a table that lists organization name, and how many workflows run by the organization are in success, failed, and cancelled states over time.
Workflow by orgs shows a colored doughnut chart that represents different organizations, and total number of workflows run by the organization irrespective of the workflow statuses. Mouse over a color to view details.
Workflow status by circle maintainers shows a table that lists workflow author names along with the how many workflows are success, failed, cancelled, and approved per author.
Workflow status by repositories shows a table that lists origin repository where the workflow is created, target repository along with the how many workflows are success, failed, and cancelled.
MTTR in last 90 days by Workflow in Hours shows a table that displays how much time (in hours) it took for a workflow to recover from the failed state. Mean Time To Recover (MTTR) displays data only for last 90 days.
By default, Empty Commits (Commits with Zero value) and Bots are filtered, however, you can include these filter values by navigating to the filter section of dashboard. For details, see Add and Manage Data Filters.
The Commits dashboard represents a set of metrics that shows high level information, such as total number of commits, authors, repositories, and so on for all repositories of the project.
Overview shows information about commits in Git repositories. For each commit, Git stores information about who and when authored the commit (author), and about the organization that included the commit in the repository.
Filter lets you filter the dashboard data by author name, organization name, and repository. Select values from the respective drop-down lists, and click Apply changes to filter the dashboard as per selection.
Summary shows the number of Commits, Authors, and Repositories of the project.
Commits Percentage By Organization shows a doughnut chart that represents the total number of commits by organization for the project. Mouse over a color in the chart to see the total number of commits by the organization, and the percentage of commits out of the total commits for the project.
Lines Changed Percentage By Organization shows a doughnut chart that represents the total number of lines of code changed by an organization for the project. Mouse over a color in the chart to see the total number of lines of code changed by the organization, and the percentage out of the total lines of code that are changed for the project.
Active Contributors shows a bar graph that represents the number of contributors per day over time. Mouse over a color in the graph to see the total number of contributors for a date.
Commits shows a bar graph that represents the number of commits per day for the project over time. Mouse over a color in the graph to see the total number of commits for a date.
Commits by Time Zone shows a bar graph with a count of commits per Coordinated Universal Time (UTC) time zone. Dates and times (author time, committer time) in Git use the time zone of the computer where the contributor performed the action. This data is used to display time zone information. Mouse over a color in the graph to see the total number of commits for each time zone.
Commits By Organization shows a bar graph that represents the number of commits by an organization per day over time. Mouse over a color in the graph to see the total number of contributors of an organization including organization's name for a date.
Lines of Code Changed By Organization shows a bar graph that represents the number of lines of code changed by an organization per day over time. Mouse over a color in the graph to see the organization's name, date, and total number of lines of code changed by the organization.
Authors shows a table that lists author name, number of commits by the author, number of projects the author has committed code to, number of lines the author has added and removed codes, and the average number of files the author has worked over time.
Organizations shows a table that lists:
Organization: name of organization
Commits: number of commits made by the organization
Authors: number of authors of the organization who made commits
Touched Files: number of files the organization has contributed towards
Added Lines: number of added lines to the code base
Removed Lines: number of removed lines from the code base
Projects: number of projects the organization is contributing towards
Repositories: number of repositories of the project the organization is contributing towards, and
Avg Lines/Commit: average number of lines added or commits made by the organization over time
Repositories shows a table that lists repository name with links, number of commits made to the repository, number of authors contributed to the repository, number of organizations contributed to the repository, number of lined added and removed to/from the code base of the repository, average number of files touched or commits made to the repository over time.
Projects shows a table that lists project names, number of commits, authors, repositories, number of added lines, removed lines, average number of lines committed, and average number of files committed per project.
Organization Commits shows a table that lets you sort values by commit hash, organization name, repository URL, author name, and date.
By default, Bot commit is filtered, and can't be included for Summary dashboard.
Summary provides a high-level metrics about each data source for which the project is configured. Following are activities for quick navigation:
Following dashboards are displayed under Technical Metrics:
Commits shows the following information:
Lines Of Code Changed represents total number of lines changed—added, updated, and deleted—for a selected time range.
Commits represents total number of commits for a selected time range.
Contributors represents the number of contributors for the project
No Of Sub Projects represents total number of sub projects (added git repositories) under a project.
Repositories represents total number of repositories of the project. This includes the number of repositories of sub projects.
Top 10 Companies By Commits shows a doughnut chart that represents **** top ten companies that contribute most to the project.
Unknown as a company name shows number/percentage of codes submitted by those contributors who are not affiliated with any organization.
Others represents a group that combines all other companies that come after top nine companies that contributes more.
Data is not available for a Git data source that is not configured for Insights.
Gerrit shows total number of changesets (both open and closed), number of open changestes, average time in hours to merge changesets, average time in days for first review of changeset, and total number of approved changesets for a selected time range.
GitHub shows total number of pull requests (both open and closed), number of open pull requests, average time in hours to merge pull requests, and average time in hours pull requests were open for a selected time range.
Top 10 Contributors By PRs (for GitHub) **** or Top 10 Contributors By Changesets (for Gerrit) **** lists the top ten individuals—that contribute most to the project— by name, total number of pull requests or changestes, and percentage of commits out of the total number of commits by the community.
Top 10 Companies By PRs (for GitHub) **** or Top 10 Companies By Changesets (for Gerrit) **** shows a doughnut chart that represents **** top ten companies that contribute most to the project.
Mouse over a color in the doughnut chart to view company name and number of commits made by the company.
Unknown as a company name shows number/percentage of codes submitted by those contributors who are not affiliated with any organization.
Others represents a group that combines all other companies that come after top nine companies that contributes more.
Jira shows total number issues that includes both open and closed issues, total number of submitters, number of open issues, average time in days the issues are open, and time in days for which a stacked area chart compares the number of issues and unique contributors per calendar period.
GitHub Issues shows total number issues that includes both open and closed issues, total number of submitters, number of open issues, average time in days the issues are open and average time in days the issues took to be resolved.
Bugzilla shows total number issues that includes both open and closed issues, total number of submitters, number of open issues, total time in days the issues are open, and time in days issues took to be closed.
Top 10 Contributors By Issues Submitted lists the top ten individuals— that contribute most to the project— by name, total number of issues, and percentage of issues out of the total number of issues submitted by the community members.
Top 10 Companies By Issues Submitted shows a doughnut chart that represents top ten companies that contribute most to the project.
Unknown as a company name shows number/percentage of issues submitted by those contributors who are not affiliated with any organization.
Others represents a group that combines all other companies that come after top nine companies that contributes more.
Following an example of Issue Management overview section for a project that uses Jira, GitHub Issues, and Bugzilla to manage issues:
Top 10 Jobs lists the top ten jobs by name, number, and percentage.
Build Results for Jenkins and Jobs Results for CircleCI shows a doughnut chart that represents total number of builds for all the build results, such as Success, Failure, Unstable, and Aborted. Click a result to exclude the data. Click again to include.
Top 10 images By Pull Count lists the top ten pulls by name, number, and percentage.
Top 10 images By Star Count lists the top ten stars by name, number, and percentage.
****:
shows analytic overview of git commits for a selected time range. Default time range is Last 90 Days. You can to view data for the selected time range.
Clicking Go To Overview and View All takes you to the respective dashboard of page.
Top 10 Contributors By Commits lists the top ten individuals—that contribute most to the project— by name, total number of lines of codes changed that includes lines of codes added and modified, number and percentage of commits. Click View All to navigate to the page.
Mouse over a color in the chart to view company name and number of commits made by the company. Click a company name to exclude company data. Click again to add the company data. Following is an example:
shows analytic overview of pull request information of GitHub repositories and/or information about changesets and patchsets per changeset for Gerrit.
Clicking Go To Overview and View All under Gerrit takes you to the respective table/graph/chart of section.
Clicking Go To Overview and View All under Gerrit takes you to the respective table/chart/graph of section.
Click a company name to exclude company data. Click again to add the company data. Following is an example:
shows analytic overview of issue management platforms used by a project, such as Jira, GitHub Issues, and Bugzilla.
Clicking Go To Overview and View All under Jira takes you to the respective table/chart/graph of section.
Clicking Go To Overview and View All under Github Issues takes you to the respective table/chart/graph of section.
Clicking Go To Overview and View All under Bugzilla takes you to the respective table/chart/graph of section.
Mouse over a color in the doughnut chart to view company name and number of commits made by the company. Click a company name to exclude company data. Click again to add the company data. Following is an example:
**** shows an analytic overview of the number of total builds, jobs, failed builds, job categories, and average build duration in minutes. Clicking Go To Overview and View All under CI/CD takes you to the respective table/chart/graph of and sections respectively.
shows total number of median pulls, average stars for images, increase number in pull count, and star counts for DockerHub. Clicking Go To Overview and View All opens the respective table/chart/graph of section.
Pull Request Management show analytics for the following data sources based on a project's source control platform:
The Jenkins dashboards under CI/CD drop-down list represents a set of metrics that show overview analysis of Jenkins data. Following are the various dashboards of Jenkins:
Overview shows an overview of Jenkins build and job data over time.
Filter lets you filter the dashboard data by job name. Select values from the drop-down list, and click Apply changes to filter the dashboard as per selection.
Summary shows the number of builds, jobs, nodes, and average time of build duration in minute for a project.
Builds Over Time shows a bar graph that represents the total number of builds per day over time.
Build Results Percentage shows a stacked bar graph that represents the percentage of build results—Success and Failures— per day over time. The build results are color coded. Mouse over a color to see the percentage of build result for a day.
Build Results By Categories shows a doughnut chart that represents the total number of builds in the project by status: SUCCESS, FAILURE, UNSTABLE, ABORTED. Mouse over a color in the chart to see the status, total number of builds for the status, and the percentage of the project's builds for that status.
Active Nodes Over Time shows a bar graph that represents the number of active nodes per day over time. Mouse over a color to see the number of active nodes for a day.
Nodes shows a table that lists name of node, number of builds, median or 50th percentile of duration in minute, and total duration in minute per node.
Builds shows a table that lets you sort values by build date and time, job name with build number (job_build), URLs for build and job, type of result, node on which the job is built, and time taken in minutes to execute the build.
Jobs shows data about Jenkins jobs such as duration, successes, and failures over time.
Filter lets you filter the dashboard data by job name. Select values from the drop-down list, and click Apply changes to filter the dashboard as per selection.
Summary shows the number of build results—Success, Failure, Unstable, Aborted.
Results shows a doughnut chart that represents the total number of jobs in the project by status: SUCCESS, FAILURE, UNSTABLE, ABORTED. Mouse over a color in the chart to see the status, total number of jobs for the status, and the percentage of the project's jobs for that status.
Jobs Per Branch shows a doughnut chart that represents the total number of jobs per branch. Mouse over a color to see the branch name, total number of jobs per branch, and percentage of jobs out of total jobs in project.
Jobs shows a bar graph that represents the number of jobs per day over time. Mouse over a color to see the total number of jobs per day.
Duration Trend shows the time in minutes for the total number of jobs per day over time and a trend line to show an increase, decrease, or stability in the job time.
Avg. Build Duration Over Time Per Job shows a stacked bar graph that represents the average time in minutes taken for the execution of a job per day. Mouse over a color to see the job names per day and average time taken for a job .
Jobs shows a table that lets you sort values by job name, number of builds per job, 50th percentile of build duration in minutes, total build duration in minutes, number of success and failure results.
Job Categories shows data about Jenkins jobs that are grouped into certain categories in a project.
Filter lets you filter the dashboard data by job name. Select values from the drop-down list, and click Apply changes to filter the dashboard as per selection.
Summary shows number of builds, jobs, nodes, and job categories for a project.
Jobs Evolution shows a stacked bar graph that represents number of builds executed per day.
Categories shows a table that lists name of categories the jobs are grouped to, total number of jobs and builds per category, and number of build results per success and failures.
Results Across Top Categories shows number of builds per category by status: SUCCESS, FAILURE, UNSTABLE, ABORTED. Top categories are listed based on the total number of builds per category.
Nodes shows an overview of Jenkins build and job data over time. It shows a table that lists and lets you sort values by node name, number of builds per node, 50th percentile of build duration in minutes, total build duration in minutes, success and failure counts of builds per node.
Build Data shows an overview of Jenkins build data over time
Builds shows a table that lets you sort values by build name, build result such as Success, Failure, and so on per build, node where the build happened, time taken in minutes for the build to be executed, and date and time when the build happened.
Click to share the path of respective dashboards.