How can i generate a report for bugs per developer

[Nawoda Herath]

Is there a way to generate a report for bugs per developer.  Let's say I have 5 developers in my team and each developer working on the individual story. end of the sprint, I wanted to see the no of bugs per the original developer

[Guilhem Dupuy]

Hello,

There is a way to do this using the Dashboards,

First, you have to create a filter in order to select the Projet and the Sprint you're interested in, as well as the issue type. In order to do so, you have to :

• Navigate to the advanced search
• Use for instance use the following filter :

Project = NameOfYourProjet AND Sprint = "NameOfYourSprint" AND issuetype = Bug

• Save this filter using the "Save As" Button

Once your filter is created, go to your Dashboard or create a new Dashboard if you don't already have one for your projet. Add a gadget like for instance the Pie Chart. In the gadget parameter, you should :

• Select the filter you just created
• Specify the "Statistics Type" as "Assignee"

And the result should be the report you're looking for,

Keep me informed if this solution helped you

[Nawoda Herath]

Thanks but this is not helping me. The reason is we have the assignee column for the resource whom working on the story/task. When the task moves from the Dev engineer to QA, the value of the column get changed. 

[Jack Brickey]

So first I would recommend not reassigning tasks from dev to QA personally. Rather, I prefer to have seperate task for QA, i.e. 

task 1 - develop aaaa ....assignee to dev

task 2 - test aaaa ..... assignee to QA

bug 1 - aaaa bug 1 .... assigned to dev

bug 2 - aaaa bug 2 .... assigned to dev

At a minimum you need to open separate Bug issues and this would allow you to filter and track these bugs as Guilhem suggests.

[Mehmet A _Bloompeak_]

Hi @Nawoda Herath ,

As an alternative solution, you can create a custom field named 'developed by' and use this field in your report.

[Bill Sheboy]

Hi @Nawoda Herath 

What problem are you trying to solve by tracking what you believe to be the "no of bugs per the original developer"?  What if the original developer is not the source of the defect?  Perhaps instead there is a process issue, lack of work/knowledge sharing, validation error, etc. creating the situation of more defects.

Understanding the problem may help the community provide feedback to solve the actual problem.

Thanks, and best regards,

Bill

[suvarna dixit]

In similar line would like to show defects per story ,and "issueFunction" is not working for our jira is there any other way