Can we add the component in the team managed project

Components really help to define in an easy way the different modules that are managed in a project. 

It is really vital for traceability and grouping all the different issues created. 

What would be the reason to have them in company managed project but not on team managed projects?

I totally get the request for components in team-managed projects. The good news is that with our Colored Label Manager, you can transform labels into functional components—giving you the same benefits, but with more flexibility. It's fully customizable, and you can even restrict label fields to match your project’s needs. It’s an easy and powerful way to streamline your workflow!

Any news on this issue?

even on the update provided by atlassion on November 2023, it is stated that we can use Compass on team managed projects

"...once you have signed up for Compass, you can add the field to your team-managed projects by searching for the “Compass” field through Project Settings.." 

but it doesn't work.

It really makes no sense in creating a new product and not letting the "next-Gen" projects use it...

+1 this would make it much easier to run team-managed projects in a larger organization

We use components to track things such as where bugs are found (in pre-prod or in production, if in production, during live testing, or by customers) and why they were missed (Missing test coverage, process breakdown, etc). 
We build dashboards from these components to determine where we can fill gaps. 
Would love the team-managed products to have them. 

Any updates, friends?

This would be so important for us!

Is there an update to bringing Compass components to team-managed projects?

+1

+1

Components are the best thing in Jira projects at my employer for structuring something
Why is this important feature not implemented in team managed projects? The free jira cloud version is almost worthless for me to organize my private life.

+ 1 Voting to add this feature to team-managed Jira

Please add this.

My products are coming from Azure DevOps where we have capabilities similar to Jira Team Managed projects but outstanding component mapping. We are able to add to the components as they are created and then sort our backlog according to components when we take on work in a sprint and write Release Notes.

I'm being asked to move my products to Jira. I need to do Team Managed projects for both products. I'll increase my workload by about 3x after a move to Jira. I'm fighting it all the way.

I'm with Phil Holmes in that I'll be encouraging our leadership to pursue something other than Jira or allowing my products to remain on Azure DevOps.

My overall take from this is that Jira had team-managed projects in development then shifted focus onto compass whilst not communicating effectively at all with their user base on this in support situations such as this ticket.  This has led to frustration and no understanding of where the team-managed projects will go whilst also pushing for people to use team-managed projects for their own feedback loop.  Components could (and should) have been added to team-managed projects to try and have like for like functionality between team and company managed.  What we have now is a way to manage projects that offers less function than the previous.  

In terms of compass, we are in the same situation as Hugh Gibson who commented 17/Jul/2023 - we have many projects company wide which are company managed and we do not wish to look to integrate compass on such a scale just to make team managed projects have the same functionality as company managed.  On top of this, to get the same functionality, we will have to pay $65k+ a year just to do the same as company managed.

It is for exactly the above which will have me look at alternative providers when our renewal date comes up.  

I need this 

https://getsupport.atlassian.com/browse/JST-929591

For team managed project its really a nice add-on. Please implement this feature on priority.

Thanks

This is definitely very much needed in team-managed projects!!

Much needed, I am surprised they did not manage to ship such an easy feature in 4 years. 

A `Component` is most useful as a 1st class structure in Jira tickets rather than self-managed custom metadata. E.g. being able to set default assignees easily is highly efficient compared to, say, managing pseudo-code in an Automation based on Labels.

Thanks for the update about Compass. It seems like an interesting product, but is not applicable to our long-running (25 years) product maintained by a small team. We're not using a distributed architecture, but our product is split into many DLLs and has an app as well as online scripts.

Our "components" don't match your fairly strict definition in Compass. We use them as a curated list of the aspect of the software package that are affected, and also the technology. So a single ticket might have components of "C++", "Order Download" and "Customer Accounts".

Labels can be used, but they aren't curated in the same way.

Atlassian seems to be investing in lots of glitzy new tech like Compass, but your long-term users are desparate for you to spend that engineering time on the core product which has many problems which add up to a poor experience every day. We've all been forced from Jira Server to Jira Cloud, and from the old issue view to the new one. I realised a little while ago that your internal teams are not using the new tech. Start dogfooding - maybe then you'll realise how bad the search is in Cloud; and how annoying US date formats are to the rest of the world.

My workaround is to make a checkbox field and manually add components to it. 

Seriously, such a simple and basic feature is under consideration for almost 4 years now?

Please Atlassian, do not remove features out of your own will; it now pains me as hell to move to cloud without having this feature; need to use labels which is quite ugly for our purpose!!

Needed definitely. Wonder why it was removed. There is a clear need to something to group and have a leader for.

Definately +1. 

Components would be useful in team-managed projects too but it would be amazing if it would be a feature that can be enabled/disabled in both team-managed and company-managed projects. 

So Atlassian's "advice" to use a company project instead, is basically telling it's customers to go suck an egg

first_time.gif

This is absurd.  This issue has been open for over FOUR YEARS and has over 1200 votes.

Components are already being tracked on a per-project basis with company-wide projects, so how hard can it be to migrate that functionality to team-based projects?

The whole point of wanting team-based projects is so that individual projects can create custom fields and labels to their hearts content without polluting the rest of the tenant as would happen with the old format projects.  So Atlassian's "advice" to use a company project instead, is basically telling it's customers to go suck an egg.

+1

+ :1000:

+1

+1

Using components to structure different parts of a product should be available in both team- and company-managed projects. Very useful and sourly missed at the moment. Please consider delivering this as soon as possible. Thanks!

Возможно, кому-то подойдет использование компонентов в Compass

https://disk.yandex.ru/i/MISkAaAQXfJvrA

При подключении Compass к Jira становится доступным указание компонента у задачи

https://disk.yandex.ru/i/3I4c8pgfrLvRqA

У компонента в Compass доступен большой функционал, гораздо больше, чем у старых компонентов

https://disk.yandex.ru/i/Iw5WKPQdxrDzrw

Good call ... I think I will unfollow all requests on the same basis.  No idea if Atlassian actually progress anything other than their own agenda.  If they do, it takes way too long ... years ...seriously!?!?!

(which is hilarious given the Agile marketplace they sell to)

I followed this for a year with no update except user comments requesting the feature. Unfollowing...

+1

+10

+1

And while Tempo reports cannot group time by Work Attributes, Component grouping is available - except for team-managed projects.

Seems like a really basic field that would work very similar to the fix versions, and if the tech is there to work for company-managed projects, then I would be baffled if it would require a large amount of work to adapt it to the more independent team-managed projects. It gives more structure and filtering in addition to epics, especially if the components have issues that are related to multiple epics or vice versa. 

Allow for a shared library to cover project groups, example, IT project have a consistent library and terminology, Sales have their own etc.

IT is hard to understand why this new board wouldn't have components. What is this big deal for Jira to add this field to allow us to track/breakdown the application by component ?   I will have to delete my project now and start from scratch to go back to be able to track/organize project by component. Thanks JIRA!

The new Compass product linking issues based on this field, this is even worst not to have it on next-gen/team-managed projects

Components is a HUGE field not to have available in team managed projects due to the auto assign functionality... I don't get why components is not available here when company managed projects allow the project administrators components access. 

Also, add components to forms as well please...

We use components extensively. We're software developers, and our main product has many different technologies ranging from SQL, C++, JavaScript, HTML, CSS, Perl and PHP. It's important that we can distinguish tickets by which area they affect, so an appropriate developer can be chosen, so we use components for that. We can also see easily which tickets affect a particular area.

An important part of that is that the list of components is locked down so they don't proliferate.

We also use labels for things like marking a ticket as chargeable to a particular customer, or having had a preliminary check by QA; or all marking all support tickets that are related if something is broken in the field. These are more ephemeral and it's important for any user to be able to create them for filtering.

That's why both are important.

In summary: having different permissions for the fields is the key benefit.

our team uses Components in HW dev projects: this allows to identify boards or system parts as components.

that would be really useful in team managed projects

I don't see the components option too. I am following a course by Udemy and the teacher is adding a component to the story I don't see on the right-hand side under the issues where he clicks and it is showing on the right-hand side of this page now.

Having only recently moved to Jira from ALM due to a (shortsighted??) company decision, the whole situation makes me laugh.  The basis of Jira is the management of Agile Development, and they take literally years to implement anything ... pretty embarrassing for them, more so that they have (absolutely necessary) features in one edition and leave them out in another.

NB people complain about ALM, but it is a (very) mature and usable product.  I have never worked in software development, and IMO the Agile methodology is unnecessary outside its core purpose (and in some cases a complete hindrance, especially with test management given some of the tools available).  It appears it is implemented because 'everyone else is doing it' so it must be the right thing to do ...right?  There is some merit to this, but perhaps purely from having skills that the job market is asking for, no matter if they are really suitable. 

Let's be real guys, this ticket is 3 years old and isn't even by far the oldest highly requested feature. It's not happening.

Voting for this feature. The labels workaround is embarrassingly brittle.

Voting in for bringing in this feature

Jira components seem to be required to link to compass components. Is there a workaround for connecting compass components to Jira issues in a team managed project? 

Wow...i recently created a Team Managed project so that we could control the workflow (my client is a business unit within a large enterprise organization and doesnt have Jira admin rights), and I completely regret taking my client in this direction.  No ability to create additional boards within a project...no components.   What's even the point of these "next gen projects?"   It seems to have plenty of downsides and Im not seeing any benefit other than I can change workflow without Jira admin rights

As a newbie to Jira, I don't have too much insight to the components, but it seems to be a feature that could have been quite useful in our scrum project (ERP Upgrade). As we have to start, the release will be too late for us to use anyway and we'll have to use labels oder custom fields to add sort of multidimensional structure to our issues. So, I'm looking forward to be able to use it in an upcoming project.

It seems so strange that this issue, with almost 1K votes, has been open for more than two years and still is not even planned to be worked on.

New to Jira in an admin role and I already see the need for this feature. It is an absolutely necessary functionality that currently has no real alternative.
On one side, Kudos for creating such an useful tool. On the other, seems like users were more aware of it's value than the creators and decision makers.

May 2021 >>> almost May 2022, and so 'the next year' is almost finished ...can we have this early 'this year'?
I find it an odd request to add a comment detailing why teams value Components, as (in my ignorance) the use cases seem quite obvious.  Using my limited understanding, Jira boards rely on filters to make them manageable ...so we need criteria to filter.  Components are well suited for this, and so it is a big gap in Team Managed capability.  Perhaps this is why people don't leave comments and simply up vote.

As I switch between Team Managed and Company Managed, I now find that I can have a drop down filter in Team Managed, but I can't in Company Managed (which has Components).  This means neither project type provides a workable solution.  I really can't work out why there is such disparity between the two types.  It is really frustrating.