Engineering Allocation Hygiene
The success of infradev in triage-ops has led to a more formal process of Engineering department collaboration using Engineering Allocations: gitlab-org&6555 (closed). The Engineering Allocation process will help ensure that cross department issues are identified, prioritized, visible and acted on.
To ensure that issues identified for Engineering Allocation are visible in the to be created tracking Dashboard, we need to ensure the following items are met and remind team members to apply the right action when they aren't:
-
Engineering Allocation in triage-ops should accompany
~Eng-Consumer::*
and~Eng-Producer::*
labels for filtering. - An Engineering allocation must have:
- An
~Eng-Consumer::*
label - An
~Eng-Producer::*
label - A
~priority::*
label - (To be confirmed) A
~severity::*
label when the type is typebug in triage-ops
- An
Proposal(s)
- A scheduled hygiene automation which will:
- Apply Engineering Allocation in triage-ops when the child
~Eng-Consumer::*
or~Eng-Producer::*
. - Nudge either the team member that applied the Engineering Allocation label if the conditions above aren't met to remind them that it's missing required labels.
- Apply Engineering Allocation in triage-ops when the child
- Migrate the nudge and default behaviors to a reaction based workflow that has a delay. For example:
- Auto apply triage-ops
19499153 when15119514 and typefeature in triage-ops~EngAllocation*
label is present similar to triage-ops - Nudge after 5 minutes for the team member that applied the label if the required conditions aren't met.
- Auto apply triage-ops
Edited by Rémy Coutable