# Problem The [Q1FY23 Create Benchmarking](https://docs.google.com/presentation/d/1jX7bOij69uS_oT2tYEsB5Rwg5A9rErfmpi7YhcY1H3M/edit#slide=id.p24) showed poor performance for branch protection operations. Since this assessment, significant improvements have been made to bring settings together into one single place under settings via https://gitlab.com/groups/gitlab-org/-/epics/8578+. However, the research has also shown that users searching the UI for how to protect branches started looking under _Repository > Branches_ rather than under _Settings_. So while the above epic made a huge contribution towards making the setting of branch protections much more understandable, it did not improve the initial discovery of these. # What remains to be done to enable an E2E workflow 1. make these settings discoverable from the place that users most frequently started their search: _Repository > Branches_ 2. Polish the Overview and the detail view of settings to cover all settings ## High level the following needs to be done: * Either adding a link to the branch page (near :one:) to point to the *overview branch rules* and with better wording than before. Or a deep link to the branch rule detail page near :two: (but that is probably next level). We can probably consider https://gitlab.com/gitlab-org/gitlab/-/issues/358209+ to be the issue that needs to be refined to address this.  # What is not part of this epic Editing the branch rules directly in the new place is part of https://gitlab.com/groups/gitlab-org/-/epics/8075+