🧩 Subcomponents for Jira 4.2.0: shared components across projects

[#1]

Jira components are project-scoped. That works fine for a single project – but once multiple projects share the same functional areas like "Authentication" or "Payments API", keeping them in sync becomes a maintenance problem. Each project gets its own copy, names drift over time, and cross-project reporting turns into a manual exercise.

Subcomponents for Jira Cloud 4.2.0 introduces cross-space (cross-project) components – the ability to define a component once and manage it across multiple projects from a single page.

⚙️ Define once, manage everywhere

With cross-space components, a Jira admin creates a component in one place, assigns it to whichever projects need it, and the app takes care of keeping everything aligned. Update the name, swap the lead, or revise the description – the change rolls out to every linked project on its own.

Under the hood, every project retains a native Jira component, so your workflows, boards, and filters carry on as usual. Subcomponents simply ties those copies together.

To get started, open Apps in the Jira left sidebar and select Subcomponents. Switch to the Cross-space components tab.

You can also reach the cross-space components page from any project – click Manage cross-space components in the toolbar on the project's Subcomponents tab.

Click Create component, give it a name, pick the target projects, and the app provisions a native Jira component in each one – linked and synchronized from that moment on.

🔄 Unify what already exists

Organizations that already have the same component scattered across multiple projects do not need to start from scratch. The app identifies components with matching names and offers to consolidate them under one shared definition. Every issue keeps its current assignment – nothing gets relocated. The admin picks which name, lead, and description to carry forward.

⚠️ Spot divergence before it spreads

If a project admin modifies a component directly in Jira's built-in Components settings, the cross-space view surfaces the mismatch – the admin can bring the local copy back in line or separate that project from the shared definition. Instead of drifting silently, differences get caught and resolved.

🔍 Query once, see everything

The GLOBAL keyword for the subcomponents() JQL function lets you query across all projects that share a cross-space component: component IN subcomponents("GLOBAL", "Component name")

The result set spans every project where that component lives – child components included – without listing individual project keys. Use it in saved filters, gadgets, or reports for a single cross-project view. Capitalization does not matter, and your existing per-project queries stay intact.

Worth a look

If your Jira components need to exist in more than one project, cross-space components address the gap that native Jira does not. There are other approaches in the ecosystem – manual sync scripts, third-party tools – and Subcomponents for Jira Cloud is one option worth evaluating. Cross-space components are available in the Advanced edition.

From the Broken Build team behind Subcomponents for Jira Cloud