<!--This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal Currently, the "Pipelines" tab in the merge request shows the pipeline in the following order. * Merge request pipelines are placed in the top. Other pipelines are placed under the merge request pipelines. * Within each pipeline type, new pipelines are placed in the top. There is no feature to change this order. For this reason, in the merge request where many pipelines are associated, branch pipelines (no matter how new they are) will “sink” below the merge request pipelines. So the option to sort pipelines by the time they were executed, regardless of pipeline type is needed. {width=962 height=762} <!--Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues.--> <!--Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section.--> <!--Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/-->