Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
You can refer to these examples to get started using INSIGHTS. These examples provide simple steps that represent how to find the dashboards and data you need.
Roles: Project Manager
Where: Bugzilla dashboards are available from the Issue Management drop-down list.
As a project manager, your team uses Bugzilla for bug tracking and for project management. You are interested in getting an overview of issues and submitters in your projects. You want to see who is submitting issues (bugs).
Do these steps:
Click a project name of interest.
From the Project Management drop-down list, select Bugzilla > Overview. A dashboard shows information about issues and submitters in Bugzilla organizations. For details, see Bugzilla > Overview.
Use the visualizations to understand aspects of Bugzilla tracking and project management. You go to Submitters to see who submits the most issues and the average open days for the issues.
Role: Technical Manager
Where: Jenkins dashboards are available from the CI/CD drop-down list.
As a technical manager of a project, you have concerns about aspects of your Jenkins jobs and builds. You want to understand what jobs and their corresponding builds have long duration times or high percentages of failures or instabilities so your team can work to increase efficiency. You may also want to know how quickly the builds are getting fixed, or if some test cases are permanently failing and either need updating or reviewing.
Do these steps:
Click a project name of interest.
From the CI/CD drop-down list, select Jenkins > Overview. A dashboard show Jenkins overview data. For details, see Jenkins > Overview.
Use the visualizations to understand various build aspects of the project. For example, each new build must go through a series of steps including compilation, testing, and validation. You want these steps to be optimized to ensure that changes are delivered quickly. The longer the build process takes, the longer it takes for changes to make their way into production. The Builds table shows the total time to complete a build (in seconds). By seeing the build time for a particular job, you can understand the build process and monitor it for abnormalities. If a build ends too quickly or takes too long, it could indicate a problem with the build server or the build pipeline.
From the CI/CD drop-down list, select Jenkins > Jobs. A dashboard show Jenkins job data. For details, see Jenkins > Jobs.
Use the visualizations to understand various job aspects of the project. Success/Failures in percentage is useful because it shows the ratio of successful jobs to unsuccessful jobs, and how healthy your jobs are in builds. You can see the build and job health as a total and see how it has changed over time.
Role: Developer, Project Manager, Community Manager
Where: GitHub issue dashboards are available from the Issue Management drop-down list.
Users who cannot submit a pull request, but encounter problems with code can submit their bugs and feature requests as issues. The number of issues, and how they are addressed, can indicate your projects’ levels of user adoption as well as how responsive maintainers are to user needs. This number depends on how issues are tracked. Consider that issues may remain open longer for a project that uses GitHub issues only for bugs rather than one that uses issues for bugs and feature requests.
This example demonstrates how you can view GitHub issues and then analyze how efficiently a project and its organizations handle the issues. How quickly a project closes issues can determine if you want to participate in the project. INSIGHTS lets you see how efficiently organizations and projects close issues.
Follow these steps:
From the Issue Management drop-down list, select GitHub > PR Efficiency. A dashboard shows GitHub efficiency data. For details see, Issue Management > GitHub > PR Efficiency.
BMI shows a multi-line graph that represents the Backlog Management Index (BMI). BMI is the number of closed issues divided by the number of open ones in a given period of time. Moving Avg. is set to 8 weeks to identify changes in trends. Average is also shown as a reference. BMI values greater than 1 mean the community is closing more issues than those they are opening. Values less than 1 mean the opposite—more issues are open than those closed during a given time frame. Mouse over this graph or Lead Time to show a line that displays the date and time at the top of the legend.
This data can help you determine if the project is one in which you want to participate.
Roles: Developers, Community Managers
Where: GitHub Pull Requests dashboard is available from the Source Control drop-down list.
Insights lets you look at the pull request contributions to the project and answer questions such as:
Who contributes to the community by submitting pull requests?
How responsive is the project to changes?
Who does the bulk of the work?
Which organizations submit pull requests for the project?
Follow these steps:
From the Source Control drop-down list, select GitHub > Pull Requests.
A dashboard shows information about pull requests for a project and organization, and information about who submitted the pull request and when. For details, see Source Control > GitHub > Pull Requests.
Use the visualizations to understand the project activity and other aspects of the pull requests:
As a developer, you can see how active a project is and the average duration that pull requests remain open. In Pull Request by Status Over Time, you note a recurring pattern of pull requests that remain open too long within a certain time frame. The length of time pull requests remain open can indicate how responsive and welcoming your project maintainers are to outside contributors. If a pull request sits for too long without response, potential contributors may go to other projects. In addition, pull request metrics depend on the size of the project. Small projects might keep the number of open pull requests at 10 or fewer. Keeping pull requests at this limit would be challenging for large projects that have lots of community input compared to the number of maintainers. Reviewing pull requests takes time so large projects tend to have longer open duration than small projects. This data helps you decide if this is a project in which you want to spend your time.
As a project maintainer, you can see the number of pull requests by submitters, organizations, and repositories. In Organizations, you look for the organization that is doing the bulk of the development effort.
Roles: Developer, Project Manager
Where: Jira dashboards are available from the Issue Management drop-down list.
You are interested in participating in a project, but first, you want to see if the project has an accumulation of uncompleted work that needs to be dealt with in the backlog.
Do these steps:
From the Issue Management drop-down list, select Jira > Backlog. A dashboard focuses on open issues, their accumulated time, and associated organization. For details, see Jira > Backlog.
View statistics about open issues in Open Issues Statistics. These statistics give you a summary of open issues in the backlog.
Find more information in the dashboard such as who the submitters are and the average days open of the issues that they submit. For example, you might notice a recurring pattern of issues that accumulate in a certain time frame.
This data can help you decide if this is a project in which you want to spend your time.
Roles: Developer, Community Manager, Project Manager
Where: Communication dashboards are available from the Chat Room and Mailing List drop-down lists.
Chat Room provides metrics of slack activity, and Mailing List provides metrics of Groups.io and Pipermail. A mailing list is a common way for project community members to interact with others in a project. Mailing lists are often set up so that all members can send to the list. Members can ask questions and get help or provide information to others on the list. A busy mailing list can be a good indicator of the health of community engagement in the project. For our analysis, we will consider Pipermail as an example here.
Do these steps:
Click a project name of interest.
Click a project name of interest that shows the GitHub logounder data sources.
On Efficiency Closing GitHub Issues window, select an organization and project from drop-down lists, and click Apply changes.
Use the resulting data to understand how efficiently issues are handled. For example, red for Time to Close indicates that committers are not attending to issues or that contributors are not providing fixes.
Repositories table shows the average time for GitHub issues to be closed for each repository in a project. Repositories with many open issues can indicate security problems.
Click a project name of interest that shows the GitHub logounder data sources.
Click a project name on a project of interest that shows the Jira logo .
Look at the data in Issues waiting to be closed and Accumulated Time (days): Issues waiting to be closed to learn about the number of issues by status over time.
From the Mailing List drop-down list, select Pipermail > Overview. A dashboard shows information about email activity in projects and who sent emails and when. Information about the corresponding organization is also provided. For detail, see .
Use the visualizations to understand aspects of mailing list activities for the project. Any conversation or discussion in a mailing list can be helpful to a project by solving bugs or even providing potential seeds for new features, new products, and so on. For example, you might be interested how active an organization's mailing list is—look at the analytics for the organization such as the Emails By Organizations doughnut chart: In another example, you hold in high esteem a community member and want to see if this person participates actively in the project—look at the Email Senders analytics.
You use Confluence for your project documentation. You are interested in getting information about Confluence activities such as the top edited pages and top editors. This information helps you identify where your documentation effort is focused and by whom.
Do these steps:
Click a project name of interest.
Use the visualizations to understand aspects of documentation activities and pages.
From the Documentation drop-down list, select Confluence > Overview. The Overview dashboard shows information about Confluence activities. For details, see .