Automation to ensure that issues and MRs with legacy team labels have a 1:1 mapping to their devops stage or group label
We need an on-going automated rule to apply devops::xxxx
to issues and MRs based on their legacy team labels.
This is the first step to ensure we can transition each groups to use the new labels.
We would want a rule that continuously runs and auto adds the new stage and group labels where these old team labels exist.
Stages
- ~Manage => devopsmanage
- ~Create => devopscreate
- ~Plan => devopsplan
- Verify => devopsverify
- ~Package => devopspackage
- ~Release => ~"devops::release"
- ~Configure => ~"devops::configure"
- ~Monitor => devopsmonitor
- ~Secure => devopssecure
- ~Defend => ~"devops::defend"
- ~Growth => devopsgrowth
- ~Enablement => ~"devops::enablement"
Groups
- ~Gitaly => groupgitaly
- ~Gitter => groupgitter
- Health => ~"group::health"
- ~Distribution => groupdistribution
- ~Geo => groupgeo
- ~Memory => ~"group::memory"
- ~Ecosystem => ~"group::ecosystem"
Phases
Merge Requests
- Add devops stage labels and (where necessary) group labels to merged Merge Requests that have a clear 1:1 mapping between legacy and stage label !184 (merged)
- This accounts for the majority of throughputs and will make them visible in the stages dashboards
- Determine devops stage label to apply to merged Merge Requests that do not have a clear 1:1 mapping
- Some MRs have several legacy labels and it's unclear which stage label should be applied
- We cannot apply two as stage labels are scoped labels
- We can use feature label inference to determine stage labels where possible and manual labelling for the outstanding MRs
- Determine devops stage label to apply to merged MRs with no legacy label
- We can infer the stage labels from the category labels where possible
- Add devops stage labels to open MRs in the same manner as 1, 2, and 3
- Not essential as only
merged
MRs are counted for throughputs
- Not essential as only
- Determine group labels for merged MRs through author
Issues
- Add devops stage labels to issues via feature label inference implemented in !155 (merged)
- We are in the process of rolling this out completely here for both issues and MRs resources
Edited by Rémy Coutable