One post tagged with "hierarchy"

Jira components were designed for a flat world: one list, no nesting, no structure. That works at ten components and collapses at fifty — when "SSO" sits next to "Platform" and "Mobile" with nothing expressing that it belongs under "Auth", which belongs under "Platform". Teams end up encoding the architecture in name prefixes and maintaining ever-growing component in (...) lists by hand. This guide covers three ways to get a component hierarchy in Jira, and what each one costs.