Prompt team member author for bugs to add severity and priority labels
We could ask team members that raise bugs to add severity and priority labels
I tested out the following rule set:
condition_label_unprioritized: &condition_label_unprioritized
labels:
- bug
forbidden_labels:
- P1
- P2
- P3
- P4
- no priority
state: opened
condition_label_unseveritized: &condition_label_unseveritized
labels:
- bug
forbidden_labels:
- S1
- S2
- S3
- S4
- no severity
state: opened
resource_rules:
issues:
rules:
- name: Prompt team members to prioritize bugs
conditions:
author_member:
source: group
condition: member_of
source_id: gitlab-org
<<: *condition_label_unprioritized
actions:
labels:
- no priority
comment: |
Hi {{author}},
Please add a [Priority label](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/contributing/issue_workflow.md#priority-labels) to this bug report.
If it's not possible for you to gauge the priority, please mention the relevant team's Engineering or Product manager
- name: Prompt team members to severitize bugs
conditions:
author_member:
source: group
condition: member_of
source_id: gitlab-org
<<: *condition_label_unprioritized
actions:
labels:
- no severity
comment: |
Hi {{author}},
Please add a [Severity label](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/contributing/issue_workflow.md#severity-labels) to this bug report.
If it's not possible for you to gauge the severity, please mention the relevant team's Engineering or Product manager
merge_requests:
rules: []
Results (at the time of posting)
Team bugs unprioritized | Team bugs unseveritized |
---|---|
684 | 644 |
- Note: This is only a test I ran for GitLab CE project
- Note: At the time of posting there are
1659
issues categorised as a bug in CE. So there would still be around 1000 issues untouched by this rule
Edited by Mark Fletcher