Add automated workflow labels to issues/MRs
We're currently using workflow::
labelling to describe what state an MR is in. For example, when an engineer starts working on an MR, they add the workflow::In dev
label to the MR. The other workflow::
labels are: workflow::in review
and workflow::verification
. The workflow for releases is currently described here
I'm proposing an iteration that would apply workflow::
labels associated with the stages: workflow::verified
, workflow::in production
. The actual names should be consistent with the workflow.
Per Eric's comment:
- So I think today when something leaves the
verification
state the label is just removed. It would be better to replace it with a label indicatingverification-passed
or something. - And to infer whether something has been deployed to prod you have to just know that because the issue was closed. It would be better to have an explicit label.
The problem I'm trying to solve is that there's a lack of awareness of these later stages in deployment resulting in Product Managers and Engineering Managers being unsure of the state of issues after the MR(s) associated them move past verification. A solution to this is intended to allow people to be aware of the status of issues they are tracking without a manual gathering process.
A potential solution I thought might work would be to utilise the GitLab Bot to update issues once MR(s) had been moved to these stages.