No of time a defect is re-assigned before resolution

[Ram Nanjun]

Hi

Quite often, defects are being re-assigned from one person to another (like throwing over the wall) without any collaboration and this cause long lead times for defect resolution.

Is there a way to pull a report e.g. for a Scrum team, get the list of defects for a time period (or) for a Sprint (or) for a Release, then how many time the defect was re-assigned to someone else and the time it took between each re-assignment before it ultimately got resolved

Trying to dig through each defect takes time, so getting this into a report fashion is what I am looking for

Thanks

[Bill Sheboy]

HI @Ram Nanjun -- Welcome to the Atlassian Community!

That type of reporting is not possible with the built-in features.  You may be able to do that with a marketplace addon for JQL and/or reporting.  You could also use the REST API to pull the changelogs (i.e. history) for issues and report in an external tool.

Without those things, I wonder why does the team think this behavior is happening?  Perhaps discuss this symptom/behavior with the team in a retrospective to learn the root causes and decide improvements to try.  For example, is this related to:

• lack of shared knowledge issue, and so people are passing issues they cannot resolve
• a measurement issue, where people are measured by having "assigned issues", and so they take items,
• a too much work in progress (WIP) issue, where people are not noticing that items are moving, person to person,
• or other causes.

One way to make this symptom visible is to ask about each defect currently on the board at each daily scrum (standup), confirm the urgency, and discuss having the team swarm on such issues.

Kind regards,
Bill