Looking for Developer Metrics around Issues - Traceability/ Dashboard Question

[Aaron Shapiro]

I'm looking to create a report that looks at the bugs being logged in a project and groups them by parent task (the work task that was put through QA) and then by the developer (that did the work on the original task). I'm trying to create a performance/ traceability report to see which of our developers are generating the most of amount of bugs with their work and what types of bugs we are typically finding. 

We ideally would like to use this to help our developers improve their skills. 

Edit: 

Right now, our structure is this 

- User Story is broken down into work tasks

- Work tasks assigned to a developer to code, then they are QA'd

- Bugs are logged against work tasks being QA'd

[Joseph Chung Yin · Accepted solution]

@Aaron Shapiro -

Out of the box, you best advise is to export your JQL search results into CSV file and use Excel to generate complex reporting needs.  There are only limited reports/gadgets available by default.

Your other recommendation is to conduct a search third party add-ons for Reporting needs from Atlassian Marketplace https://marketplace.atlassian.com/.

One that we utilize is EasyBI Reports and Charts for Jira -https://marketplace.atlassian.com/apps/1211051/eazybi-reports-and-charts-for-jira?tab=overview&hosting=cloud

This is very powerful/function rich add-on allowing users to create multi-dimension data cube to generate complex reporting/charting needs.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

[Manuel]

Hi @Aaron Shapiro ,

I agree that if you want to make a custom report, then eazyBI can be the better choice.

Test management tools  *may* provide some reports for traceability, like the Traceability report in Xray; all inside Jira.