Report - User with most unresolved issues assigned per project

[daveys110]

I'm trying to get a feel for the "most knowledgeable" person per project over the whole organization.

I'm imagining a table or chart listing the project, user & issue count... but showing only a single row per project - i.e. the most "active" (or most assigned at least) user per project.

How can I do this?

[Liam Green]

Hi @daveys110 

It wouldn't be possible to show only the top person per project per row.

What you could do is create a dashboard showing a list for each of your projects - then an overall list showing all projects.  

Regards, Liam

[Nic Brough -Adaptavist-]

I am a little fuzzy on how this might work, as I don't know your process or data, but if I assume:

• You have a pile of projects, containing lots of issues, and people fixing stuff
• An issue that is assigned to someone is eventually "resolved", and the assignee remains the person who either did it, or was in charge of getting it done, and so could be assumed to be knowledgeable about that issue

To do the basic report, I would

• Go to issue search and search for "Project in (x, y, z) and resolution is not empty"  (I don't care what fields it shows or the order for this purpose, but you might find it useful to set them up to suit you when you come back to it)
• Save this as a filter with a explanatory or useful name, such as "all expertise"
• Go to Dashboards and add a new one.  Probably want to make this one a single column in the layout
• Add a "two dimensional" gadget to it.  Configure the gadget such that:
  • It uses your filter
  • X-axis = Project
  • Y-axis = Assignee
  • Include resolved issues

When you save that gadget, you will see a grid showing you the number of issues that have been resolved by person and project.  I'd guess that the highest numbers broadly correspond with the people who know that project best.

I went with X/Y that way round because you probably have a lot more people than projects.

[daveys110]

The problem with this approach is that every person gets a row... so it's not just the "top" / "most assigned" users.

So if I have a busy project "PROJA" and the least-active user has 10 unresolved issues; but the quiet project "PROJB" has the most-active user with 1 unresolved issue; it makes it very difficult to see once you go beyond a small number of users.