Administering / Monitoring Users' activity / issues

sonarqube
issues

(Gonzalo Vasquez) #1

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
    Community Edition Version 7.4 (build 18908)

  • what are you trying to achieve
    I’m trying to get a dashboard where I can I see all our users’ with their issues count both from old and new code, similar to the home view which shows similar info but group by projects and, then once clicking into a user, I’d like to see a breakdown on which those user’s issues are distributed between projects. The goal of this is to encourage users to get their issues fixed in a proactive way

  • what have you tried so far to achieve this
    I think I’ve searched everywhere I can think of without finding anything but closely related to what I’m trying to achieve


(Wouter Admiraal) #2

Hi @gvasquez-waypoint,

Right now, there’s no way for anyone to see a summary of other users’ issues. What we encourage is that users take ownership and responsibility, and use the My Issues page to keep track of what requires attention (go to the global Issues page, and then filter by “My issues”).

We do have web services for these, though, in case you’d like to make your own dashboard. This would allow you to fetch all issues, across all projects, for a given user. For example:

GET /api/issues/search?s=FILE_LINE&authors={author_email}&resolved=false

You can navigate to http://your-sq-instance.com/web_api/ to see the documentation for the webservices.

What we also have, in the Enterprise edition, is a suite of Governance features, which allows organizations to keep a bird’s eye view of overall quality across projects and/or teams. However, I’m not sure this is what you’re looking for, as it doesn’t focus on individual users, but teams. It also tracks reliability ratings rather than issue counts (which makes sense: 100 issues on a +1M LOC project is not the same as 10 issues on a 1K LOC project).

But in the end, teams should – ideally – be encouraged to take action on issues, not out of pressure, but out of a sincere desire to improve the quality of their code :slight_smile:. This is why the Fixing the Water Leak philosophy is so important.