Hygiene assurance on merge request throughputs

Right now we allow multiple team labels per issue, this may complicate throughputs when it comes to MRs.

We are trying to explore automation to enforce this for issues see !61 (merged)

We will have to do the same for MRs as well. I think issues is a place where we allow this grey area of collaboration.

MRs should be more defined with clear expectations. This needs to balance with the accuracy we want out of throughput.

I would rather enforce this per labels on MRs instead of adding more backend logic to insights. It could mean one or more of the following.

  • Enforce just one team label for MRs
  • Do the mapping directly in MRs so the data is transparent. Its easy to fix labels than opening up the insights postgres DB.

Update

From my comment in #84 (comment 117359383) it should be ok to have overlapping throughputs as engineers from 2 teams collaborate and work on the same MR.

Proposal

  • Add gitlab triage to automatically add the author's team label on an MR => Superseded by #141 (closed).
  • Add gitlab triage bot to nag that one of these labels are applied if there are none

/cc @markglenfletcher

Edited by Rémy Coutable