Add community MRs sections in "Merge requests requiring attention" group report
requested to merge 565-add-community-contributions-needing-attention-to-the-weekly-mr-needing-attention-group-report into master
-
This renames the "Idle merge requests" group report to be "Merge requests requiring attention" report.
-
This adds two new sections to the report, focused on Community contribution:
- "Unassigned community merge requests" => DRI isn't clear on unassigned MRs, so depending on the case, MRs should be assigned to authors (if changes are required), or to a reviewer/maintainer/coach.
- "Idle community merge requests (updated more than 28 days ago)" => The goal is to ensure idle MRs moves forward (or are closed). This excludes WIP/Draft MRs.
Expectations
From the latest dry-run at https://gitlab.com/gitlab-org/quality/triage-ops/-/pipelines/193123384.
| Group | Unassigned community merge requests | Idle community merge requests (updated more than 28 days ago) |
|---|---|---|
| ~"group::access" | 9 | 1 |
| groupacquisition | 0 | 0 |
| ~"group::analytics" | 0 | 0 |
| ~"group::apm" | 0 | 0 |
| ~"group::certify" | 0 | 0 |
| groupcompliance | 1 | 0 |
| groupcomposition analysis | 0 | 0 |
| ~"group::configure" | 0 | 0 |
| ~"group::container security" | 0 | 0 |
| ~"group::continuous integration" | 8 | 2 |
| ~"group::conversion" | 0 | 0 |
| groupdatabase | 0 | 0 |
| groupdistribution | 0 | 0 |
| groupdynamic analysis | 0 | 0 |
| ~"group::ecosystem" | 7 | 0 |
| ~"group::editor" | 0 | 1 |
| ~"group::expansion" | 0 | 0 |
| ~"group::fulfillment" | 0 | 0 |
| ~"group::fuzz testing" | 0 | 0 |
| groupgeo | 1 | 0 |
| groupgitaly | 4 | 0 |
| groupgitter | 0 | 0 |
| groupglobal search | 0 | 0 |
| ~"group::health" | 0 | 0 |
| ~"group::import" | 11 | 1 |
| ~"group::insider threat" | 0 | 0 |
| groupknowledge | 1 | 0 |
| ~"group::memory" | 1 | 0 |
| ~"group::package" | 5 | 0 |
| grouppipeline authoring | 0 | 0 |
| ~"group::portfolio management" | 1 | 0 |
| ~"group::progressive delivery" | 0 | 1 |
| groupproject management | 3 | 3 |
| ~"group::release management" | 0 | 0 |
| ~"group::retention" | 0 | 0 |
| grouprunner | 0 | 0 |
| groupsource code | 4 | 1 |
| groupstatic analysis | 0 | 0 |
| ~"group::static site editor" | 0 | 0 |
| ~"group::telemetry" | 0 | 0 |
| ~"group::testing" | 2 | 0 |
| groupthreat insights | 0 | 0 |
| groupvulnerability research | 0 | 0 |
Examples
From dry-run at https://gitlab.com/gitlab-org/quality/triage-ops/-/jobs/751367594:
Hi, @jlear @donaldcook
This is a group level merge requests report. This report contains:
- Open team MRs updated more than 28 days ago
- Open unassigned community MRs
- Open community MRs updated more than 28 days ago
> Please review these merge requests to identify if there are any steps that can shorten the time to merge, such as reminding the author or reviewers about it, marking it as draft or closing the MR.
Weekly idle merge request trends by group can be found here: https://app.periscopedata.com/app/gitlab/663398
----
## Idle team merge requests (updated more than 28 days ago)
- [ ] @annabeldunstone - `https://gitlab.com/gitlab-org/gitlab/-/merge_requests/18034` Truncate the beginning of the project path names on issue boards ~"Category:Issue Boards", ~"devops::plan", ~"frontend", ~"group::project management", ~"section::dev"
## Unassigned community merge requests
- [ ] https://gitlab.com/gitlab-org/gitlab/-/merge_requests/38985 Add verify step to uploads migration to object storage details ~"Community contribution", ~"Object Storage", ~"devops::plan", ~"documentation", ~"group::project management", ~"section::dev"
- [ ] https://gitlab.com/gitlab-org/gitlab/-/merge_requests/36711 WIP: Monkey patch around issue #227783. ~"1st contribution", ~"Community contribution", ~"devops::plan", ~"group::project management", ~"section::dev"
- [ ] https://gitlab.com/gitlab-org/gitlab/-/merge_requests/31565 WIP: Add no default visibility option on project, group, snippet pages ~"Community contribution", ~"database", ~"database::review pending", ~"devops::plan", ~"group::project management", ~"section::dev"
## Idle community merge requests (updated more than 28 days ago)
- [ ] `https://gitlab.com/gitlab-org/gitlab/-/merge_requests/27425` Give feedback when using quick actions that have no effect ~"Community contribution", ~"backend", ~"devops::plan", ~"frontend", ~"group::project management", ~"section::dev"
- [ ] `https://gitlab.com/gitlab-org/gitlab/-/merge_requests/25442` Modification of the position of the anchor ~"Community contribution", ~"devops::plan", ~"frontend", ~"group::project management", ~"section::dev"
- [ ] `https://gitlab.com/gitlab-org/gitlab/-/merge_requests/25048` Issue.move_between now moves before and after to the end if they have nil relative_position ~"1st contribution", ~"Community contribution", ~"Hackathon", ~"backend", ~"devops::plan", ~"group::project management", ~"section::dev"
----
Note: Using full links to the merge requests will update the merge request
which will remove them from the future report.
/label ~"group::project management"
/label ~"triage report"
/assign @jlear @donaldcookAction items
-
(If applicable) Add documentation to the handbook pages for Triage Operations => gitlab-com/www-gitlab-com!63188 (merged) - (If applicable) Identify the affected groups and how to communicate to them:
-
/cc @ person_or_group=> -
Relevant Slack channels => -
Week-in-review
-
Closes #565 (closed).
Edited by Rémy Coutable