Subcomponents for Jira Cloud was migrated to Atlassian Forge in 4.0.0, bringing enhanced security for users.
Forge also allowed us to introduce several features that were not feasible before:
- Automated migration with JCMA for users migrating from Jira Data Center to Jira Cloud.
- Feature parity improvements between Data Center and Cloud, including the REST API and Packages on the issue view.
Enhanced security
For any third-party app landing on Jira Cloud, the honest answer to "where does the app's data live?" used to require a functional architectural diagram, an external AWS environment, and a full security review – the kind of package that takes weeks to assemble and months to approve. Cloud approval programs with hard budget deadlines don't have weeks. One enterprise Jira admin put it plainly in support:
"The Information Security Team is requesting Functional Architectural Diagrams so we can approve SubComponents for Jira Cloud in the migration program... We need the diagram now to help secure approval, as they have hard deadlines for budget approval."
In 4.0.0, Subcomponents for Jira is now a Forge app. Core Subcomponents data is stored and processed on Atlassian's cloud platform and follows the Forge data-residency model. This can simplify security discussions for organizations that prefer Atlassian-hosted apps, while each organization remains responsible for its own security and compliance assessment. The app is now eligible for Atlassian's Runs on Atlassian program – the programmatic marker InfoSec teams increasingly look for as a first-pass approval signal. See Subcomponents for Jira Cloud 4.0.0 release notes for the full changelog.
Automated migration with JCMA
For users still on Data Center and planning to move to Cloud, Forge unlocked a second benefit: Subcomponents app data now migrates automatically via the Jira Cloud Migration Assistant (JCMA) (see the Subcomponents for Jira DC 3.16.0 release notes). Before 4.0.0, the Jira migration itself went through JCMA (Atlassian's canonical tool, already installed and trusted). But Subcomponents app data – component hierarchies, component versions, packages, related admin configuration – had to be recreated by hand on the Cloud side. That's fine for a single project. It scales poorly at ten.
JCMA now moves supported Subcomponents app data as part of a standard Jira migration. Install and configure JCMA in your Data Center Jira, include app data in the migration plan, and Subcomponents configurations can be transferred to Cloud automatically. As with any migration, validate the migrated data in the target site.
Feature parity with Data Center
For Cloud customers already running Subcomponents at enterprise scale, and for teams landing on Cloud via JCMA, this release closes two important gaps between the Data Center and Cloud versions of Subcomponents: REST API access and Packages on the issue view. It also includes property-page performance improvements. See the Subcomponents for Jira Cloud 4.0.0 release notes for the full changelog.
REST API
Subcomponents for Jira Cloud now provides a REST API for programmatic access to subcomponents, component-version mappings, packages, property values, and settings. It is intended for teams that need to integrate Subcomponents data into their own tools or automate supported administration workflows. The API uses Atlassian OAuth 2.0 (3LO) and is documented in the in-app interactive API reference.
Packages on the issue view
Packages linked to an issue’s Fix Versions now appear directly in the issue view. The panel sits alongside other issue-view apps and refreshes when the issue’s component or version relationships change. This gives reviewers, release managers, and engineers the relevant package context while they work on the issue, without requiring them to navigate to a separate Subcomponents screen.
Performance improvements
Component and version properties pages – where a Jira admin defines the fields that hang off every subcomponent hierarchy – used to load in up to a minute on the large instances that hold the most schema-heavy data. On the Forge platform, that rebaseline was a one-time delivery opportunity: fresh code paths, no legacy performance debt. Properties pages that took up to a minute at 800–1000-component scale now load in seconds. For customers coming off Data Center at that scale, the properties page is the first thing they touch when they check Cloud parity, and it now behaves the way they expect a production admin surface to behave.
What that means
Subcomponents for Jira 4.0.0 moves the app to Forge, adds REST API access, shows Packages in the issue view, and improves property-page performance. For Data Center customers, JCMA can now transfer supported Subcomponents app data as part of a standard Jira migration. Together, these changes make the Cloud app easier to operate and integrate with supported workflows.
Subcomponents for Jira Сloud 4.0.0 is available on the Atlassian Marketplace; existing installs upgrade automatically.
.png)
