Atlassian Forge app for Jira Cloud

Team Components for Jira

Components for team-managed spaces: one managed list per space, searchable with JQL and ready for board filters.

USD 6 per month for 1–10 users in one Jira Cloud instance. Larger teams use graduated pricing. Free evaluation for at least 30 days, subject to Atlassian billing terms. Pricing and trial details.

The Components page in Jira space settings: a list of components with descriptions and the number of work items that use each one.
The component list in Space settings → Apps → Components, with the number of work items per component.

A component list for every space

Team-managed spaces have no Components field. Add one: space admins keep a list of components with descriptions, see how many work items use each one, and import existing labels.

Consistent names, searchable with JQL

Select components from the space's managed list to keep names consistent. Search with JQL, save filters and add custom filters to your board.

Rename and merge with progress tracking

Apply name changes to affected work items, subject to Jira permissions. Review failures and resume unfinished changes. Archive components you no longer use.

Cloud pricing and free evaluation

Current Jira Cloud app version: 2.3.0, released on . See the Marketplace version information.

For one Jira Cloud instance, the monthly subscription costs USD 6.00 total for 1–10 users. Prices are in USD; larger teams use graduated user bands.

Users in the bandMonthly charge
1–10USD 6.00 total, flat rate
11–100USD 0.60 per user in this band
101–250USD 0.45 per user in this band
251–1,000USD 0.20 per user in this band
1,001–100,000USD 0.10 per user in the later displayed bands

Charges accumulate across bands. For example, 11 users cost USD 6.60 per month; 250 users cost USD 127.50 per month. The annual 1–10-user tier is USD 60.00 per year; annual prices for other team sizes use Atlassian's annual tiers.

Free evaluation: at least 30 days. The end date can align with Atlassian's recurring billing cycle; this is not a permanently free plan or a fixed expiry date for every customer. See Atlassian's evaluation terms.

Pricing checked in Marketplace on 2 November 2026. See the Marketplace listing for availability and current estimates, including any applicable taxes, currency conversion or discounts.

What it adds to Jira

Add a space-specific component catalog and a component picker to team-managed Jira spaces. Jira's built-in Components field is available in company-managed spaces; Team Components provides a separate custom field for team-managed spaces.

  • Components (team-managed): a field you add to any team-managed space. It is searchable with JQL and works in saved filters and board custom filters.
  • Space settings → Apps → Components: add, describe, rename, merge, archive and delete components, import existing labels, and find values that are not in the list.
  • Bulk changes with progress tracking: rename, merge or remove component values on affected work items, subject to Jira permissions. Keep the browser open, review failures and resume unfinished changes. Update saved filters that use old names manually.

How it handles your data

  • The app is built on Atlassian Forge and runs on Atlassian's platform. It has no backend and no servers operated by PPFTEC.
  • The component list is stored in Jira itself, as a property of the space. The chosen components are stored on the work items, in the app's field.
  • During normal app use, Jira requests run through Atlassian Forge in the current user's context. The app has no PPFTEC-operated backend or external runtime database and does not send its catalog or field values to PPFTEC app servers. Support correspondence is handled separately.

App data, support correspondence and website hosting are separate activities. Details: Privacy policy.

Requirements

  • Jira Cloud, team-managed spaces.
  • Operating system: any operating system with a Jira Cloud-supported desktop browser. Team Components runs inside Jira in the browser; no native Team Components desktop installation is required. See Atlassian's supported browsers.
  • Permissions requested by the app: read:jira-work, write:jira-work and manage:jira-project. The app can only do what the signed-in user can already do in Jira.

Links