Remove untriaged issues report (!1983) · Merge requests · GitLab.org / Quality Department / triage-ops

Lee Tickett requested to merge gitlab-community/quality/triage-ops:remove-untriaged-issues-report into master Feb 17, 2023

What does this MR do and why?

Now contributor success don't have capacity to work the untriaged issues, we need to stop the report.

Expected impact & dry-runs

Schedule update: https://gitlab.com/gitlab-org/quality/triage-ops/-/jobs/3788945849

🏗 Schedule `[3-hour] gitlab-org/gitlab encourage issue self-triage` wasn't found, we'll create it. 🏗
⛑ [ReadOnlyComClient] Creating a pipeline schedule with: gitlab-org/quality/triage-ops, {:active=>true, :cron=>"5 */3 * * *", :cron_timezone=>"UTC", :description=>"[3-hour] gitlab-org/gitlab encourage issue self-triage", :ref=>"master"}... ⛑
	🏗 Variable 'TRIAGE_SOURCE_TYPE' wasn't found, we'll create it. 🏗
⛑ [ReadOnlyComClient] Creating a pipeline schedule variable with: gitlab-org/quality/triage-ops, , {:key=>"TRIAGE_SOURCE_TYPE", :value=>"projects"}... ⛑
	🏗 Variable 'TRIAGE_SOURCE_PATH' wasn't found, we'll create it. 🏗
⛑ [ReadOnlyComClient] Creating a pipeline schedule variable with: gitlab-org/quality/triage-ops, , {:key=>"TRIAGE_SOURCE_PATH", :value=>"278964"}... ⛑
	🏗 Variable 'TRIAGE_UNTRIAGED_ISSUES' wasn't found, we'll create it. 🏗
⛑ [ReadOnlyComClient] Creating a pipeline schedule variable with: gitlab-org/quality/triage-ops, , {:key=>"TRIAGE_UNTRIAGED_ISSUES", :value=>"1"}... ⛑

Policy: https://gitlab.com/gitlab-org/quality/triage-ops/-/jobs/3788945845

********************************************************************
Executing policies from policies/stages/report/untriaged-issues.yml.
********************************************************************
Performing a dry run.
=============================
Triaging the `278964` project
=============================
---------------------------------------
Processing summaries & rules for issues
---------------------------------------
-------------------------------------------------------------------------------
Gathering resources for rule: **Encourage the self triage of untriaged issues**
-------------------------------------------------------------------------------
.[DEBUG] query_api: https://gitlab.com/api/v4/projects/278964/issues?per_page=100&not%5Blabels%5D=automation%3Aself-triage-encouraged&state=opened&created_after=2023-02-16
[DEBUG] rate_limit_infos: Rate limit remaining: 1999 (reset at 2023-02-17 09:03:04 +0000)
.[DEBUG] query_api: https://gitlab.com/api/v4/projects/278964/issues?per_page=100&not%5Blabels%5D=automation%3Aself-triage-encouraged&state=opened&created_after=2023-02-16&page=2
[DEBUG] rate_limit_infos: Rate limit remaining: 1998 (reset at 2023-02-17 09:03:04 +0000)
* Found 125 resources...
* Filtering resources....[DEBUG] query_api: https://gitlab.com/api/v4/groups/9970/members?per_page=100
[DEBUG] rate_limit_infos: Rate limit remaining: 1997 (reset at 2023-02-17 09:03:05 +0000)
.[DEBUG] query_api: https://gitlab.com/api/v4/groups/9970/members?per_page=100&page=2
[DEBUG] rate_limit_infos: Rate limit remaining: 1996 (reset at 2023-02-17 09:03:06 +0000)
.[DEBUG] query_api: https://gitlab.com/api/v4/groups/9970/members?per_page=100&page=3
[DEBUG] rate_limit_infos: Rate limit remaining: 1995 (reset at 2023-02-17 09:03:06 +0000)
.[DEBUG] query_api: https://gitlab.com/api/v4/groups/9970/members?per_page=100&page=4
[DEBUG] rate_limit_infos: Rate limit remaining: 1994 (reset at 2023-02-17 09:03:07 +0000)
.[DEBUG] query_api: https://gitlab.com/api/v4/groups/9970/members?per_page=100&page=5
[DEBUG] rate_limit_infos: Rate limit remaining: 1994 (reset at 2023-02-17 09:03:08 +0000)
.[DEBUG] query_api: https://gitlab.com/api/v4/groups/9970/members?per_page=100&page=6
[DEBUG] rate_limit_infos: Rate limit remaining: 1993 (reset at 2023-02-17 09:03:08 +0000)
.[DEBUG] query_api: https://gitlab.com/api/v4/groups/9970/members?per_page=100&page=7
[DEBUG] rate_limit_infos: Rate limit remaining: 1992 (reset at 2023-02-17 09:03:09 +0000)
.[DEBUG] query_api: https://gitlab.com/api/v4/groups/9970/members?per_page=100&page=8
[DEBUG] rate_limit_infos: Rate limit remaining: 1991 (reset at 2023-02-17 09:03:09 +0000)
.[DEBUG] query_api: https://gitlab.com/api/v4/groups/9970/members?per_page=100&page=9
[DEBUG] rate_limit_infos: Rate limit remaining: 1990 (reset at 2023-02-17 09:03:10 +0000)
.[DEBUG] query_api: https://gitlab.com/api/v4/groups/9970/members?per_page=100&page=10
[DEBUG] rate_limit_infos: Rate limit remaining: 1990 (reset at 2023-02-17 09:03:11 +0000)
.[DEBUG] query_api: https://gitlab.com/api/v4/groups/9970/members?per_page=100&page=11
[DEBUG] rate_limit_infos: Rate limit remaining: 1989 (reset at 2023-02-17 09:03:11 +0000)
.[DEBUG] query_api: https://gitlab.com/api/v4/groups/9970/members?per_page=100&page=12
[DEBUG] rate_limit_infos: Rate limit remaining: 1988 (reset at 2023-02-17 09:03:12 +0000)
.[DEBUG] query_api: https://gitlab.com/api/v4/groups/9970/members?per_page=100&page=13
[DEBUG] rate_limit_infos: Rate limit remaining: 1987 (reset at 2023-02-17 09:03:12 +0000)
.[DEBUG] query_api: https://gitlab.com/api/v4/groups/9970/members?per_page=100&page=14
[DEBUG] rate_limit_infos: Rate limit remaining: 1986 (reset at 2023-02-17 09:03:13 +0000)
.[DEBUG] query_api: https://gitlab.com/api/v4/groups/9970/members?per_page=100&page=15
[DEBUG] rate_limit_infos: Rate limit remaining: 1985 (reset at 2023-02-17 09:03:14 +0000)
.[DEBUG] query_api: https://gitlab.com/api/v4/groups/9970/members?per_page=100&page=16
[DEBUG] rate_limit_infos: Rate limit remaining: 1984 (reset at 2023-02-17 09:03:14 +0000)
.[DEBUG] query_api: https://gitlab.com/api/v4/groups/9970/members?per_page=100&page=17
[DEBUG] rate_limit_infos: Rate limit remaining: 1983 (reset at 2023-02-17 09:03:15 +0000)
.[DEBUG] query_api: https://gitlab.com/api/v4/groups/9970/members?per_page=100&page=18
[DEBUG] rate_limit_infos: Rate limit remaining: 1982 (reset at 2023-02-17 09:03:16 +0000)
.[DEBUG] query_api: https://gitlab.com/api/v4/groups/9970/members?per_page=100&page=19
[DEBUG] rate_limit_infos: Rate limit remaining: 1981 (reset at 2023-02-17 09:03:16 +0000)
.[DEBUG] query_api: https://gitlab.com/api/v4/groups/9970/members?per_page=100&page=20
[DEBUG] rate_limit_infos: Rate limit remaining: 1980 (reset at 2023-02-17 09:03:17 +0000)
.[DEBUG] query_api: https://gitlab.com/api/v4/groups/9970/members?per_page=100&page=21
[DEBUG] rate_limit_infos: Rate limit remaining: 1979 (reset at 2023-02-17 09:03:18 +0000)
.[DEBUG] query_api: https://gitlab.com/api/v4/groups/9970/members?per_page=100&page=22
[DEBUG] rate_limit_infos: Rate limit remaining: 1979 (reset at 2023-02-17 09:03:18 +0000)
.[DEBUG] query_api: https://gitlab.com/api/v4/groups/9970/members?per_page=100&page=23
[DEBUG] rate_limit_infos: Rate limit remaining: 1979 (reset at 2023-02-17 09:03:19 +0000)
* Total after filtering: 3 resources
* Limiting resources...
* Total after limiting: 3 resources
The following comments would be posted for the rule **Encourage the self triage of untriaged issues**:
# https://gitlab.com/gitlab-org/gitlab/-/issues/391925
```
Hey @tamasgal, thank you for creating this issue!
To get the right eyes on your issue more quickly, we encourage you to follow the
[issue triage best practices](https://about.gitlab.com/handbook/engineering/quality/issue-triage/#partial-triage-checklist).
**PLEASE NOTE**: You will need to use the
[`@gitlab-bot label command`](https://about.gitlab.com/handbook/engineering/quality/triage-operations/#reactive-label-command)
to apply labels to this issue.
To set expectations, GitLab product managers or team members can't make any promise if they will proceed with this.
However, we believe [everyone can contribute](https://about.gitlab.com/company/mission/#everyone-can-contribute),
and welcome you to work on this proposed change, feature or bug fix.
There is a [bias for action](https://about.gitlab.com/handbook/values/#bias-for-action),
so you don't need to wait. Try and spin up that merge request yourself.
If you need help doing so, we're always open to [mentor you](https://about.gitlab.com/community/contribute/mentor-sessions/)
to drive this change.
*This message was [generated automatically](https://about.gitlab.com/handbook/engineering/quality/triage-operations).
You're welcome to [improve it](https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/policies/stages/report/untriaged-issues.yml).*
/label ~automation:self-triage-encouraged
```
# https://gitlab.com/gitlab-org/gitlab/-/issues/391924
```
Hey @finkandreas, thank you for creating this issue!
To get the right eyes on your issue more quickly, we encourage you to follow the
[issue triage best practices](https://about.gitlab.com/handbook/engineering/quality/issue-triage/#partial-triage-checklist).
**PLEASE NOTE**: You will need to use the
[`@gitlab-bot label command`](https://about.gitlab.com/handbook/engineering/quality/triage-operations/#reactive-label-command)
to apply labels to this issue.
To set expectations, GitLab product managers or team members can't make any promise if they will proceed with this.
However, we believe [everyone can contribute](https://about.gitlab.com/company/mission/#everyone-can-contribute),
and welcome you to work on this proposed change, feature or bug fix.
There is a [bias for action](https://about.gitlab.com/handbook/values/#bias-for-action),
so you don't need to wait. Try and spin up that merge request yourself.
If you need help doing so, we're always open to [mentor you](https://about.gitlab.com/community/contribute/mentor-sessions/)
to drive this change.
*This message was [generated automatically](https://about.gitlab.com/handbook/engineering/quality/triage-operations).
You're welcome to [improve it](https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/policies/stages/report/untriaged-issues.yml).*
/label ~automation:self-triage-encouraged
```
# https://gitlab.com/gitlab-org/gitlab/-/issues/391915
```
Hey @yuesheng0723, thank you for creating this issue!
To get the right eyes on your issue more quickly, we encourage you to follow the
[issue triage best practices](https://about.gitlab.com/handbook/engineering/quality/issue-triage/#partial-triage-checklist).
**PLEASE NOTE**: You will need to use the
[`@gitlab-bot label command`](https://about.gitlab.com/handbook/engineering/quality/triage-operations/#reactive-label-command)
to apply labels to this issue.
To set expectations, GitLab product managers or team members can't make any promise if they will proceed with this.
However, we believe [everyone can contribute](https://about.gitlab.com/company/mission/#everyone-can-contribute),
and welcome you to work on this proposed change, feature or bug fix.
There is a [bias for action](https://about.gitlab.com/handbook/values/#bias-for-action),
so you don't need to wait. Try and spin up that merge request yourself.
If you need help doing so, we're always open to [mentor you](https://about.gitlab.com/community/contribute/mentor-sessions/)
to drive this change.
*This message was [generated automatically](https://about.gitlab.com/handbook/engineering/quality/triage-operations).
You're welcome to [improve it](https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/policies/stages/report/untriaged-issues.yml).*
/label ~automation:self-triage-encouraged
```

Action items

If adding environment variables for reactive processors, update config/triage-web.yaml and .gitlab/ci/triage-web.yml
(If applicable) Add documentation to the handbook pages for Triage Operations =>
(If applicable) Identify the affected groups and how to communicate to them:
- /cc @person_or_group =>
- Relevant Slack channels =>
- Engineering week-in-review

Edited Feb 17, 2023 by Lee Tickett

Remove untriaged issues report

What does this MR do and why?

Expected impact & dry-runs

Action items

Merge request reports