Draft: Move issues workflow
What does this MR do and why?
This MR will remove the Issues workflow page from the development contributing guidelines:
- This page is not just for contributors but also pertains to team members
- It is not a helpful guide to making issues and mostly just series of links back to the handbook
- Some of the content may also be outdated.
Sections of the Issues workflow page will be moved into the handbook as appropriate and directly into the issue templates if it makes sense. Everything else can be removed.
Related Issues
Related to:
- technical-writing#744 (closed)
- https://gitlab.com/gitlab-org/quality/contributor-success/team-task/-/issues/162
Issues Workflow Page Outline
SECTION | NEW LOCATION |
---|---|
Issue workflow summary | This MR moves to issue template |
Issue Triaging | already in handbook https://about.gitlab.com/handbook/engineering/quality/issue-triage/ |
Labels | Update: moved to its own Labels page on docs.gitlab.com |
Feature Proposals | This MR moves to issue template |
Issue Weight | is this used? put in issue template? |
Regression Issues | Already exists in handbook: https://about.gitlab.com/handbook/engineering/quality/triage-operations/onboarding/#onboarding-checklist |
Technical and UX debt | Update: moved to new Labels page on docs.gitlab.com |
Technical debt in follow-up issues | ? |
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Daniel Murphy