Code Analytics: Allow filtering by group, subgroup, project, modifier, label

Problem to solve

Even though it's great to have full picture of code hot spots, many EMs only care about their portion of the infrastructure. Many companies divide their teams using groups, subgroups and projects so we need to allow filtering by these. We would also like to allow filtering by file and 'authors'/'assignees', i.e. someone that has modified the file. It might be the case that code hotspots are driven by 1 person which has inherited a lot of old entangled code and we would like to have a way to represent that. If we build on a fragile base, we want to make sure this is a deliberate decision by management.

Intended users

EMs

Further details

Proposal

For the label, it would be interesting to see if bugs/features/refactoring are focused on the areas we find as hotspots or with high complexity or temporal coupling.

Permissions and Security

Documentation

Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Links / references

Edited Nov 14, 2019 by Dan Jensen
Assignee Loading
Time tracking Loading