Eliminate Confusion around editing optional Approval Rules in MR
Release notes
In the past you've noticed that our default approval rules (Optional Approval) still showed up when editing an MR. Now we are much clearer about the difference between standard and optional approval rules and don't bother you showing optional approval rules when editing MRs in projects that have them.
Problem to solve
Users are confused about the display of approval rules when editing MRs, when those approval rules are optional.
Intended users
User experience goal
Proposal
Don't display optional approval rules when presented with options to edit approval rules (specifically in the MR widget) and default to some other empty state content that displays that there are no required approval rules setup for the project.
Further details
Permissions and Security
Documentation
Availability & Testing
Available Tier
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Links / references
Edited by 🤖 GitLab Bot 🤖