Skip to content

Draft: Move stranded issue sections

Daniel Murphy requested to merge update-workflow into master

Why is this change being made?

This MR unblocks gitlab-org/gitlab!112860 (closed)

  • It updates the workflow labels link to new labels page
  • It moves the Technical Debt in Follow-up Issues section (from Issue Workflow) to the Engineering Workflow page
  • It moves the Issue Weight section (from Issue Workflow) to the Engineering Workflow page

The old Issue Workflow page under contributing docs is being removed as it was not actually an issue workflow or contributing guide. The Labels section was moved to its own page and what remained were additional sections about issues that were mostly duplicated from the handbook. The 2 remaining sections without a home were Issue Weight and Technical Debt in Follow-up Issues.

If these sections could be moved to the Engineering workflow handbook page it would help to finalize the removal of the old Issue Workflow page and prevent duplication. If they cannot be added to the Engineering workflow handbook page they still need a new home and gitlab-org/gitlab!112860 (closed) will stay blocked.

Author Checklist

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

Merge request reports