Following is a rundown of the features now available under Issues -> Stats once you have connected your GitClear account to Jira or Github Issues.
First, you probably noticed that one of the new tabs added for v3 was the "Issues" tab:
The "Issues" tab focuses on what kind of work your team is focusing on as time passes
A few areas to point out here. The first is the Stats tab, which presents a richly detailed illustration of 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.
Following the Issues Types graph, the lower section of the Stats tab 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.
We also snuck in a feature that has been awaited for the better part of a year: Story Point connection. Assigning "Story Points" to a task is a popular estimation technique used by Agile teams. Developers meet and work together to agree on how much work each ticket represents. Leveraging the group's collective wisdom makes this one of the most effective known planning tactics.
If you are connected to Jira and you visit
Issue tracking, you can set up Story Point tracking here:
Settings for Jira connection, now allows specifying which field is used for Story Points
What will we use it for?
Story Points capture the amount of work projected from the issue tracker side.
Line Impact captures the amount of work completed from the code side.
You can probably see where we're going with this. Each team that sets up Story Points will learn their conversion rate from Story Points -> Line Impact. This helps project managers connect their developers to the Jira tickets that play to the developer's strengths.
Knowing the estimated Story Points for a ticket means we can ballpark what the Line Impact for that ticket will be. We can use this signal many ways. We will soon notify managers when a ticket's Line Impact has meaningfully exceeded the projection based on Story Points. Further down the road, we will use Story Points to improve Line Impact itself -- by choosing measurement changes based on whether they increase how tightly our metric corresponds with customer judgement.
Try it out and let us know what you think!