### Target persona Central DevOps team in large organizations ### Problem Maintainers are unable to view where each component is used across projects pipelines ### User Stories **Identifying outdated component versions** As a user, I want to quickly identify which projects and pipelines are using outdated versions of components, so I can ensure all components are up-to-date. User Value: This feature helps users maintain consistency and security across projects by ensuring all components are current. **Updating and notifying teams** As a user, I want to be able to update and notify teams that are not using the latest component versions, so everyone is informed and can take necessary actions. User Value: This feature facilitates communication and collaboration, ensuring that all teams are aware of updates and can synchronize their work. **Identifying missing components** As a user, I want to quickly identify if any pipelines are missing required components, so I can take corrective action to complete the pipelines. User Value: This feature ensures the completeness and functionality of pipelines by identifying and addressing missing components. **Learning about component usage adoption** As a user, I want to learn about the usage adoption of components, so I can understand how widely each component is used across projects. User Value: This feature provides insights into component popularity and adoption, helping users make informed decisions about component development and support. **Supporting component lifecycle** As a user, I want to support the component lifecycle with the removal and deprecation of old versions, so I can ensure that only supported versions are used. User Value: This feature helps maintain a clean and manageable component ecosystem by phasing out outdated versions and encouraging the use of supported ones. **Assessing the impact of changes** As a user, I want to assess the potential impact of a change, so I can make informed decisions and minimize disruptions. User Value: This feature allows users to anticipate and mitigate the effects of changes, ensuring smoother transitions and stable operations. **Tracking changes and downstream effects** As a user, I want to track changes and learn if my changes affect any additional downstream projects using the components, so I can address any issues promptly. User Value: This feature ensures that users are aware of the broader implications of their changes, allowing for proactive issue resolution and improved project stability. <details><summary>Click to expand</summary> ### User value With this feature, 1. Users will be able to quickly identify which projects and pipelines are using outdated versions of components 2. Update and notify teams that are not using the latest component 3. Will be able to quickly identify if any pipelines are missing required components and take corrective action. 4. Learn about usage adoption of component 5. Support component lifecycle with removal and deprecation of old version 6. Users could asses the potential impact of a change 7. Users could track changes and learn if their changes effect any additional downstream projects that are using the components </details> ### Design board - [Figma for sharing purpose](https://www.figma.com/design/t5Ru4qsAUhiRdnAngkoiow/CI-CD-Catalog---post-GA?node-id=862-15896&t=IjFCfJS1ZYZkzvL1-1) ### Related issues https://gitlab.com/gitlab-org/gitlab/-/issues/208957 https://gitlab.com/gitlab-org/gitlab/-/issues/356724