Health Status Triage Bot Feedback Issue 🤝🏽
Summary
In gitlab-org/quality/triage-ops#1074 (closed), we implemented a triage bot job to automatically update Health Status on issues when certain rules are triggered (see rules) for use by internal GitLab team members on GitLab issues.
We are asking internal teams to provide feedback about both the Health Status feature and the automation in this issue, so we can continue to iterate and make Health Status useful throughout the dev cycle.
Why? Health status not only allows the signaling of risk on the individual issue level, but this information rolls up into multiple workflows you and your teams are already using! And now that we’ve created an automated triage :gitlab-bot: policy, we’ve reduced the manual intervention needed to get started.
Who is this for? The rules in triage bot are signaling the likelihood that an issue is not going to ship in the current milestone. So this is a great tool for dev and pm to communicate with each other in an async way as part of normal workflow. However, the triage bot policy is flexible and can be modified to suit the needs a variety of use cases.
I’m not sold. Fair enough, but I ask you to give me 7 minutes to convince you by watching this walkthrough of ways you can utilize health status in your existing workflows!
Triage bot policy
Below are the current health status triage policy rules.
- Where the ~"Track Health Status" is applied
- The issue is assigned to the current milestone
- If the issue has no assignee by the 6th of the month, set
needs_attention - If the issue has no assignee by the 14th of the month, set
at_risk - If the issue is open but without the workflowin review in review or workflowverification labels after the 14th, set
at_risk
- If the issue has no assignee by the 6th of the month, set
Feedback
Please explain how you are using health status in your workflow in the table below. The cycle for this will be a full milestone+ and we'll look for your feedback on this issue by 2022-11-30.
Dogfooding Groups 🐶
| Group | Feedback POC | Brief description of how you're using Health Status |
|---|---|---|
| grouppipeline execution |
@jheimbuck_gl @carolinesimpson |
2022-11-02 - Applied to all issues in the latest milestone. |
| ~"group::billing and subscription management" |
@tgolubeva @rhardarson |
tbd |
| groupproduct planning |
@amandarueda @kushalpandya |
tbd |
| ~"group::authentication and authorization" |
@hsutor @adil.farrukh |
Applied to all issues in the 15.6 milestone. |
| ~"group::certify" |
@mmacfarlane @jarka |
2022-11-29 - Applied to Issues in 15.6 and continued into 15.7 |
| groupcode review | @mnohr | tbd |
| groupstatic analysis | @amarpatel | tbd |
| this could be you | ||
| add your group here | ||
| the more the merrier |