A lot of the issues that we are facing with the MR pipelines tab is because we have both REST calls and Apollo ones. Apollo has all that we need built-in and the right data is available across all components. A few reasons to do this migration: 1. Easier integration with new components (for example, the pipeline mini graph re-work) 2. Fixing and being able to deliver the failures widget https://gitlab.com/groups/gitlab-org/-/epics/11038 3. Increased performance in initial loading time as we could load data progressively 4. Ability to improve on that page and iterate faster 5. Fix a few issues where data would get out of sync between the Merge request page and the pipelines tab For example, if we used Apollo for everything, then https://gitlab.com/gitlab-org/gitlab/-/issues/419107 ould become irrelevant as Apollo cache would always be up to date. On top of that, https://gitlab.com/gitlab-org/gitlab/-/issues/418156 would also be closed because we **can** fetch trigger jobs from our graphQL queries. https://gitlab.com/gitlab-org/gitlab/-/issues/419112 is also dependant because right now, we can only know if a pipeline has failed **builds** and not bridges, so we might now show the widget at the right time. For these reasons, this issue will migrate the pipelines tab in the merge request page to Apollo For transparency, the first version of this feature came out of hackathon and had no issue. Here are the links to the MRs: 1. https://gitlab.com/gitlab-org/gitlab/-/merge_requests/122914 2. https://gitlab.com/gitlab-org/gitlab/-/merge_requests/122917 3. https://gitlab.com/gitlab-org/gitlab/-/merge_requests/122921 4. https://gitlab.com/gitlab-org/gitlab/-/merge_requests/123086 **NOTE:** Remaining MVC work is being moved to https://gitlab.com/groups/gitlab-org/-/epics/15133 for targeted visibility for technical roadmap planning.