I want to find out all bugs that a developer resolved in a particular release using jira query .

[Abhisek]

generally a bug is assigned to a developer; once the developer fixes the bug, it is assigned to the qa for testing. so if i use developer name in assignee as part of jira query, it will not give me the result. so i want to know, how to find out all tickets that a developer works on a particular sprint or release using jira query or any other way .

[Bill Sheboy]

Hi @Abhisek 

For the Assignee field, the built-in WAS IN operator could be used; then add your other criteria by Sprint, Fix Version, etc.

For example, to find work items to which I was assigned in the current sprint:

project = MYPROJECT
  AND assignee WAS IN ("Bill Sheboy")
  AND sprint IN openSprints()
  ORDER BY Key ASC

I used the WAS IN operator so my display name could be preserved without it converting to the user ID value.

Please also see the JQL functions to help with the other criteria.

Kind regards,
Bill

[Benjamin]

HI @Abhisek ,

You can use the was operator to look for issues that was assign to the developer.

JQL = assignee WAS "john.doe"

then you can add the particular release or sprint in the JQL to narrow down your search.

Ideally, the task should be by one assignee. Now, you can use Teams in cloud. Especially, this would be use for when assignee is out and requires someone to step in from the same team. 

Hope this helps.

[Arkadiusz Wroblewski]

Hello @Abhisek 

With Marketplace apps you have more options than with native JQL alone. At some places JQL are just limited and we must live with it.

Especially apps for issue history / time in status / enhanced JQL can help here, because native JQL can tell you that a bug was assigned to a developer, but not always reliably that the developer actually resolved it after QA reassignment.

Tools in that area are for example JQL Search Extensions, Status Time Reports / Time in Status, or reporting apps connected to Power BI / Tableau. These can usually analyze lifecycle/history data much better than standard Jira reporting.

Just take a look at the Marketplace, get a trial version, and see what helps you.

The important part and Trap 🪤: even with an app, exact “resolved by” reporting is best when that value is explicitly stored in the process, for example via workflow or automation.