How to capture the count of defects fixed by a Developer?

[Srilata Meka]

Hi,

We would like to capture the count of 'Closed Issues' fixed by a developer. Indirectly encouraging Unit Testing before QA deployment. Is there a way to report the number of issues resolved per developer over a certain period of time?

Thank in advance!

[Jack Brickey · Accepted solution]

Hi Srilata, there likely are a number of ways to do this but the best solution is the one that works for you and your team and moreover it depends on the details of your implementation, e.g. workflow. With that said here is some input for you.

Assuming the Assignee of a closed issue reliably equates to the developer then you could create a filter like this - assignee = currentuser() and resolution = done. Now here are some important bits: you would need to be setting the Resolution field and you would want to ensure you include all resolution codes that equate to actually solving the issue. For example, you would not want to include "Could not reproduce", "Won't do", etc. So you might change the filter to - assignee = currentuser() and resolution not in ("could not reproduce", "won't do", declined, ...). Note- i chose Currentuser() so that the filter works for whomever is viewing the results. You could leave this off and using a Dashboard gadget, e.g. two-dimensional display the count by user - x-axis = status and y-axis = assignee. You might wish to exclude certain assignees (non-developers); groups/roles work well here.

If I can better understand your precise situation I might be able to zero in with a better answer/solution.

[Srilata Meka]

Thank you @Jack Brickey for the response.

In our case, once the Issue is fixed, it is assigned to the QA resource. So now the Assignee equates to QA resource & not developer.

[Jack Brickey]

Yep...was suspicious of this which is what drove my comment on it depends on the details. So in this case I would probably create a custom user picker field (Fixed By) and when the developer actually fixes an issue then the field is updated w/ their name. Now how you do this will depend on more details. You could automatically do this if there is sufficient conditions to reliably determine "fixed" or you could have the developer set this when they transition it to the 'ready for QA' status using a Validator and requiring the field be set.

[Srilata Meka]

Thank you very munch @Jack Brickey for prompt response. I too was thinking on the same lines.