<!-- 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 --> Often times when breaking down a problem there are multiple steps which are order dependent or related. This epic captures issues necessary to allowing an epic to be marked as `Related to`, `blocking` or `blocked by` other Epics. ### Vision Currently we are providing dependency mapping between Issues via https://gitlab.com/groups/gitlab-org/-/epics/2032. As we expand our ability to map issue to each other, we need to elevate this functionality to the Epic level to : 1. Enable high level planning at the Epic level by allowing you to map Epics as dependencies of other Epics 1. Enable in depth project planning by providing inherited dependencies between Epics 1. Support the long term Portfolio Management vision of mapping Critical Dependency paths across multiple groups and projects ### MVC and follow-up Iterations 1. Enable users to assign an Epic as `related to` `blocking` or `blocked by` another epic (*replicate current Issue relation functionality)* 1. Enable an Epic to Issue, Issue to Epic relationship mapping 1. Enable Epics to automatically map dependencies between each other when their children issues are marked as `blocking` or `blocked by` another issue 1. Surface blocking relationships at the Epic level to help users quickly gauge risk