How to create Components in team-managed (Next-gen) projects

Owned by Nikki Zavadska
Last updated: Apr 25, 2024 by Michelle Ruoff
2 min read

New Jira project naming convention

Next-gen projects were renamed to team-managed projects. On the other hand, Classic projects are now called company-managed. To read more about this change, see https://community.atlassian.com/t5/Jira-articles/Two-ways-we-re-simplifying-how-to-create-projects-in-Jira/ba-p/1625982.

Do you use team-managed projects but you're missing the Components functionality there? Octo unlocks Jira Components in team-managed projects so you can use them in company-managed projects.

How does Octo store information about the team-managed components?

Octo stores components in your Jira the same way components in the company-managed projects are stored together with the link between components and issues.

Therefore, when Components will be enabled as a default functionality in team-managed projects, you’ll already have all your component data available there ☑️.

How to access Components page in team-managed projects

Next Gen component

You can access team-managed (former Next-gen) components from the Project navigation menu. Here you can view all components from the project, create new, and edit or delete existing ones.

  1. Open the Jira issue and click the component button above the Description field.

components dropdown menu

  1. The Components field appears under the Description.

  2. You can now select the component from the project by choosing a component from the drop-down.

If you can’t find a relevant component, create a new one in Project Components or in Octo.

Filter by issues linked to the component in (Next-gen) projects

There are two ways to filter by components in team-managed (former Next-gen) projects.

1. You can filter by Component field using JQL or basic filter. For example:

component = Button

2. Or you can filter by octo-component property, for example:

issue.property[octo-component].content ~ "Button"

In both of these examples replace Button with the name of your component. In case filtering by Component field (option 1.) does not work on your instance, you can always filter using properties (option 2.)