Skip to content

Link directly to bug fixes, performance, and usability improvements issue lists from the release post

Brian Rhea requested to merge link-to-bugs-ux-performance into master

Why is this change being made?

In &2056 we defined a number of ways to reduce the complexity and inefficiency of the release post production process.

Linking directly to filtered lists for Bugs, Performance, and Usability improvements will eliminate the need for the release post manager to monitor those MRs.

This MR:

  • Updates the release post template to link to closed issues in the associated milestone with relevant labels for each type
  • Removes the MR template that previously collected the list of related issues
  • Removes the MR creation from the automation
  • Updates the release post MR template to provide guidance for the teams to ensure closed issues have the appropriate labels
  • Updates the release post handbook page to remove references to the previous MRs
  • Updates the release post handbook page to provide guidance on how the release post links to filtered lists

Example links per type

Before

image

image

After

image

Closes: Product#5158 (closed)

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.
Edited by Brian Rhea

Merge request reports