Can I add Components to a team-managed project?

[James A Rosen]

My company-managed projects have a Components section in their project settings at https://company.atlassian.net/plugins/servlet/project-config/PROJECT/administer-components

But my team-managed projects don't have that and I don't see a Components feature in https://company.atlassian.net/jira/software/projects/PROJECT/settings/features

[Bill Sheboy · Accepted solution]

Hi @James A Rosen 

Team-managed projects (formerly called Next-Gen) do not have components yet.  Here is the suggestion to add the feature, which you may watch and/or vote for:

https://jira.atlassian.com/browse/JSWCLOUD-17601

Best regards,

Bill

[Nikki Zavadska _Appfire_]

Hi @James A Rosen ,

depending on what you're using components for there are a few workarounds mentioned here in the community that you can use.

The workarounds include custom fields, labels, and Automation for Jira. Because some teams are looking for experience as close as possible to components in company-managed projects we also build in the support for team-managed projects into our Component Management plugin Octo.

You can read an article with research that I've done on this topic that includes all workarounds mentioned above 👉 How to create Components in team-managed (former Next-gen) projects 

I hope this helps!

Nikki

[James A Rosen]

One of the things I'd like to use Components for is customizing permissions. I have a consultant who should only be able to see a subset of a project. I'm happy to configure that subset based on a custom field, a label, or anything else. For some reason I thought a Component was the right way to do that, but when I look at Issue-Level Security Schemes, they don't seem to have anything to do with components.

[Nikki Zavadska _Appfire_]

That's an interesting use case for components and when I think about it, it does make sense 🤔

I checked if there is some way to customize permissions like this but I didn't find any. What some teams do in this scenario is that they manage work in separate projects so they can set permissions accordingly only to certain groups for that projects.

Not sure if that's something you could do?

[James A Rosen]

The problem with separate projects (which is what we're using now) is that they're necessarily separate boards, which means we can't track velocity and burndown in one place.

[Jan Busscher]

When you create a a custom field for components, I want to sort them by the component type and I cannot.