The following is a rundown of the features now available under Issues -> Stats once you have connected your GitClear account to Jira or Github Issues.
GitClear offers many types of stats for Jira users. Here are an overview of what stats are available:
The "Issues" tab focuses on what kind of work your team is focusing on as time passes
This graph let you see which types of issues have been getting worked on over time. If you see your team is trending toward more time spent on bugs, that can be a warning signal that the PR or QA processes deserve a look.
How much of the team's change energy has been directed toward "Documentation" and "Tests"?
Viewing Diff Delta allocated toward maintaining high code quality
Teams with an Elite plan can also view their "Documentation" and "Test" work relative to industry benchmarks.
Seeing which issues have consumed the most developer energy
The "Progress by Issue Identifier" graph shows how much Diff Delta has been spent on various tickets over the time range selected, for the repos and team chosen.
Technically more of a "Code Quality" stat than an "Issue" stat per se, we present it among the issue stats so that a manager can easily see the breakdown of how energy has been spent lately:
What types of changes has the team been making lately?
Pursuant to GitClear's widely cited research on AI Copilot Code Quality, teams often want to see the extent to which their developers' changes are "Moved" (refactored) code vs "Copy/Pasted," "Deleted," and other types of code.
The "Browse" tab under "Issues & Defects" holds our "Top projects by month" table. It shows the biggest ticket that got worked on each month during the past year:
Top projects worked on in the past 12 months for Alloy. If you use Amplenote, prepare for a most spectacular leap forward in the next month or two (nominal integration with Google Calendar)
This used to be listed under "Project Tasks" when a committer was selected, but it makes more sense here. The "Domain Experts" tab helps Project Managers connect Jira tickets with the most prolific developer in the domain of the ticket. Here's how it looks for Facebook:
If you need some C++ contributed for your Facebook project, talk to Samuel. Pascal is a better fit if you're considering Android.
Filtering down to a developer or team shows how they fare across all the code 300+ code domains that GitClear currently recognizes.
Does your team use Story Points to estimate the size of upcoming issues? GitClear will automatically calculate the correlation between your Story Point estimate and Diff Delta, which can help your team improve its estimation accuracy over time. Read more about integrating with Story Points here.