### Problem to solve Often, when going to a MR the first thing you want to do is see the review app, but this can be buried and hard to find especially if the description is long. To give an example, on https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/35984 I have to press page down 11 times before I can see the review app link.  This was made worse by sometimes changing the review app link to be sometimes "View App" and sometimes "View Previous App" because you no longer have a single string you can reliably search for on the page to find the button. Even if this is fixed by https://gitlab.com/gitlab-org/gitlab/merge_requests/22024, though, I think it's still worth considering making the View App button more visible and always easy to find. ### Intended users Any user of review apps as part of their merge request workflow. ### Further details <!-- Include use cases, benefits, and/or goals (contributes to our vision?) --> ### Proposal In 12.7 we changed the way the overview/commits/pipelines/changes bar works by sticking it to the top of the screen, making it always easy to find and use. We should put the review app link on the bar in order to make it super easy to navigate to the review app without having to excessively scroll.  ### Permissions and Security N/A ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements If this feature requires changing permissions, this document https://docs.gitlab.com/ee/user/permissions.html must be updated accordingly. --> ### Testing <!-- What risks does this change pose? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? See the test engineering process for further help: https://about.gitlab.com/handbook/engineering/quality/test-engineering/ --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### What is the type of buyer? <!-- Which leads to: in which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#four-tiers --> ### Links / references <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->