Subcomponents: Component Hierarchy/Release Packages for Jira

We merged same-name components from several projects into one cross-space component without changing existing issue assignments. The automatic merge suggestions were especially helpful during cleanup.

The subcomponents() JQL function lets us report on a parent component and all its children. This removed a large amount of manually maintained JQL from our dashboards.

The hierarchy picker on the issue form gives users context at the point of data entry. Adoption improved because people no longer had to know the exact component name before selecting it.

Component versions and packages let us model releases around product modules instead of one flat project-level version list. The progress bars make it easy to see which package is actually close to completion

Cross-space components solved a real maintenance problem for shared services such as Authentication and CI/CD. We update the lead or description once and keep the native components synchronized across projects.