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

Discussion: Should users be able to apply new approval rules to an existing MR?

Context

As part of the UX Scorecard (gitlab-design#441 (closed)), a first usability test around GitLab's Merge Request page showed that the approval rules can be difficult to understand. We followed up with a usability testing study (ux-research#270 (closed)) to investigate this further and uncover new insights.

Objective

The purpose of this issue is to discuss whether there are cases where it's beneficial to apply approval rules to existing Merge Requests. It might be useful to see any data/conversations related to customers upgrading due to approvals.

Some potential cases:

  • After upgrading to a higher paid tier and gaining access to the MR approvals feature, users may need to update all open, existing MRs to keep processes consistent
  • When a user has just discovered the MR approvals feature and would like to enforce a new approvals policy without having to manually update each Merge Request in the project --> bulk update?