PPFTEC
ENRO

Team Components for Jira

Support and documentation

How to set up and use Team Components for Jira, answers to common questions, known limitations and how to reach us.

1. Installation

A Jira site administrator installs the app from the Atlassian Marketplace: Settings (gear icon) → Apps → Explore more apps, search for Team Components for Jira and choose Get app.

2. Set up a space

Team-managed spaces only show the fields their admins add. In each space where you want components:

  1. Open Space settings → Fields and click Add field.
  2. Select Components (team-managed) and click Add 1 field.
  3. Open Work types, choose a work type and click Components (team-managed) in the right panel. Click Save changes. Repeat for every work type that should have components.

Until the field is added, the Components page shows these steps as a reminder.

3. Manage components

Space admins open Space settings → Apps → Components.

  • Add component: a name (up to 255 characters) and an optional description.
  • Edit: change the description, or rename. A rename is written to every work item that uses the component.
  • Merge: move all work items of one component to another and remove the first one from the list. A work item that already had both keeps it once.
  • Archive: hide a component from the picker. It stays on existing work items and in search. Restore brings it back.
  • Delete: an unused component is deleted at once. For a used one, the app first removes it from its work items; their other components stay as they are.
  • Import…: paste a list (one per line or comma separated), or load the labels used in the space.
  • Find unlisted values: shows values on work items that are not in the list (for example set through the REST API) and lets you add them.

Renames, merges and deletions run in your browser: keep the page open until the progress bar finishes. If it is interrupted, a Resume button appears and updates only the remaining work items.

4. Components on work items

On a work item, click the Components (team-managed) row to open the picker, tick the components and click Save. The picker only offers the space's active components. Values that are not in the list stay on the work item until someone removes them.

Use the field in JQL by name or by id, for example:

  • "Components (team-managed)" = "Checkout"
  • "Components (team-managed)" in ("Checkout", "Search")
  • "Components (team-managed)" is EMPTY

On a team-managed board, add it under Space settings → Custom filters. A click on the number of work items in the Components page opens the matching search.

6. FAQ

Does it replace the built-in Components field? No. Jira offers the built-in field only in company-managed spaces. Team Components is a separate field; built-in reports that use the native Components field do not include it.

Where is the data stored? In Jira: the list as a property of the space, the values on the work items. Nothing is stored outside Atlassian.

Who can manage the list? Space admins. Anyone who can edit a work item can pick components on it.

What happens to saved filters after a rename? Filters that search for the old name must be updated by hand.

What if two admins edit the list at the same time? The second save is refused, the page reloads with the other admin's change and you can try again. Nothing is overwritten.

7. Known limitations

  • Up to 250 components per space and 100 components per work item.
  • The field is not the native Components field: native component reports, component leads and default assignees do not apply.
  • Bulk updates run in the browser and update work items one by one; large spaces take a while.
  • Not tested yet: company-managed spaces, Jira Service Management spaces, the create dialog of every work type.

8. Contact

E-mail support@ppftec.com. We answer on business days, usually within one business day. Please include your Jira site URL, the space key and a screenshot. Do not send work item content with personal data unless it is needed to reproduce a problem.