[go: up one dir, main page]
Skip to content

Merge Request... Boards?

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Description

Merge Requests have distinct flows to them. But that flow tends to be unique to individual team (with some likely commonalities). For my team, it looks something like:

      [Prep]
Author Self-Reviews &
comments for reviewers        
        |
        ˅
    [Discussion]
  Early Feedback
  (used with WIP)
        |
        ˅                      
    [Review]         <--        [Rework]
Author thinks it is        Reviewers requests
    it to merge      -->        applied
        |          
        ˅
     [Done]
   Merged/Closed

It is difficult to see what stage of the review workflow a given review is in. Does it need my attention? Am I waiting for the Author to finish some changes?

If only GitLab had already solved the problem of visualizing custom workflows and simply transitioning items from one state to another... 😸

Proposal

Implement concepts of "issue boards" for Merge Requests.

Links / references

Documentation blurb

Use cases

  • Simple transition from one state to another. Much more fluid than turning on this label, and off that label.
  • Quick representation of state of the reviews you are involved in
  • Team Leads: See if reviews are stacking up for projects
  • Team Members: See what reviews are awaiting early feedback without messing with filters

Feature checklist

Make sure these are completed before closing the issue, with a link to the relevant commit.

Edited by 🤖 GitLab Bot 🤖