Skip to end of banner
Go to start of banner

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

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Current »

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. You can read about this change here.

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

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 have all your component data already available there ☑️.

How to access Components page in team-manage projects

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.

Link issues to components in team-managed (Next-gen) projects

Have Jira issue detail open

  1. Find the component button above the Summary field.

  2. Click on the Component button.

  3. The component filed appears under the description.

  4. You can now select the component from the project by clicking on the field and choosing a component from the dropdown.

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.)


Have questions? We’re here to help! Raise a request for support:https://appfire.atlassian.net/servicedesk/customer/portal/11.

  • No labels