## Problem There are many different models that customers follow to determine how work items should relate to each other. Our current hierarchy of nested epics is very powerful, but there's also a need for a more strict hierarchy in order to adhere to frameworks like SAFe. It's also become expected functionality since many of our competitors offer it. ## Proposal * Provide a way for customers to model the rules for parent/child relationships. * Example: Epic -> Feature -> Story -> Bug. In this example, you could not have an Epic be the parent of a Bug. * Provide out of the box hierarchies that adhere to industry-standard frameworks * Allow customers to set their own hierarchies