Improve language around modifying project approval rules

Problem to solve

There is ambiguous language around the creation/modification of project approval rules. This can be confusing to adjust and worth reconsidering the language used.

Intended users

Persona: Development Team Lead

Further details

Proposal

Improve language around adding approval rules to clarify the distinction between "Adding approvers" and "Adding approval rules"

Image_2019-06-17_at_16.34.58

Permissions and Security

No change to existing permissions

Documentation

Testing

No changes to automated testing, only copy changes

What does success look like, and how can we measure that?

Improve usability and speed of feature adoption when adding/modifying project approval rules

What is the type of buyer?

GitLab Premium

Links / references

Assignee Loading
Time tracking Loading