Filter to count bugs per developer

[Jaqueline da Silva Nicolau]

Hi!

I need to see in my QA dashboard the number of bugs that a developer created during a period of time. Currently I have this filter that returns to me the tasks that generate a bug (so I can count the number of taks with bugs per developer in the dashboard)

project = ProjectKey AND issueFunction in parentsOf("issueType = "Bug" AND created >= "2023/09/01"")

But I need to change to see the number of bugs (subtask) without missing the information of who was the developer of the task that generated the bug.

I can use ScriptRunner Enhanced search or JQL only.

[Danut M _StonikByte_ · Accepted solution]

Hi @Jaqueline da Silva Nicolau,

You could use the Two Dimensional Filter Statistic gadget configured to use a filter that returns the bugs. Configure the gadget to display statistics by Reporter and Issue Type.

project = ProjectKey AND "issueType = "Bug" AND created >= "2023/09/01"

As a result, it will display the count of the bugs for each reporter. 

Hope this helps. 

Danut

[Jaqueline da Silva Nicolau]

Hi, the reporter of bugs is not the developer, so it woudn't show what I need :/ 

[Danut M _StonikByte_]

Hi @Jaqueline da Silva Nicolau,

If the bug is assigned to a developer and remains assigned to him/her after closure, you can configure the gadget to display statistic by Assignee instead of Reported. 

Danut. 

[Jaqueline da Silva Nicolau]

But the developer working in the bug is not always the same as the developer that originated the bug. That's my struggle.

[Bill Sheboy]

Hi @Jaqueline da Silva Nicolau 

Adding on to the answer from Danut M...

You note measuring "bugs that a developer created".  How do you know this information?  Is it the user who created the issue (i.e., Jira field Creator), or some other field?  You note it is not the Reporter or Assignee?

Kind regards,
Bill

[Jaqueline da Silva Nicolau]

Hi Bill, I have a field in the parent item, that has the name of the developer (it's set when the developer transition the issue to "in progress") I need the value of this field "developer" and the count of bugs the task has. So in my dashboard would show something like this:

    Name                                        Count of bugs

----------------------------------------------------------
Developer 1                                             4

Developer 2                                             1

Developer 3                                             0

[Bill Sheboy]

Thank you for that information.

Have you tried what Danut M suggested using your custom field, except inverting the axis selections?  For example:

• using a saved filter which only returns Bug issue types
• use the Two-Dimensional Filter gadget with the x-axis as Issue Type and the y-axis as your Developer custom user field?

[Jaqueline da Silva Nicolau]

the formatting is not the problem, but where the information is, if I use a filter that returns all the bugs, It won't show me who the developer that cause the bug was, because this info is in the parent of the bug (the issue that generated a bug), not the bug itself

[Bill Sheboy]

To use the built-in gadgets, the issues must contain the data you need, not the parent of the issue.  Keeping with that structure, you could:

• investigate marketplace addons which are capably of that type of reporting
• copy the developer information to the child issue (i.e., Bug) to use the built-in gadgets

As a follow-up question: you note the developer information is stored in the parent issue of the Bug.  Is there ever a case when multiple developers work on something, and so the Bugs created could apply to the work of different people?

[Jaqueline da Silva Nicolau]

Hey Bill! Happy new Year!

How could I copy the developer information, is it possible through JMWE?

And about your question, no, we create 1 task for 1 developer, so it's a trustable info

[Bill Sheboy]

Happy New Year, @Jaqueline da Silva Nicolau 

I have not used JMWE, and cannot answer that.

You could copy the field with the built-in Automation for Jira rules.  Please look here to learn more about that feature of Jira Cloud:

https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/

[Jaqueline da Silva Nicolau]

Your idea worked perfectly, thank you so much! I configured the workflow to copy the value when a trasition happen (creation in that case) and that solved my problem.

[Bill Sheboy]

Awesome! I am glad to learn that helped.