Meanwhile, have you considered creating views (the '+' at the top, below the main menu) to show specific pipeline groups?
Also, and this is a bit off-topic perhaps, do you have stages and jobs in the pipelines for each of these components? Context - I've seen setups where teams come over from using Jenkins/Bamboo and are conditioned to treat a job or a set of jobs in a single stage as a "pipeline" (perhaps because of the multi-job plugin conditioning in Jenkins). When I work with them, I show how to re-organise their jobs into stages and pipelines, and then leverage pipeline templates to reduce the maintenance across component types as well.
-- Ram