Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Can component be used to identify/track work based on team specific?

Scenario: I use one Scrum board to manage multiple projects (Each Project as an Epic). With teams as Software, Mechanical, Electrical for example

Can component be used to identify/track work based on team specific?


Component 1 = "Software"

Component 2 = "Electrical"

Component 3 = "Mechanical"

Just trying to understand if the component could only be used to group the sub projects/sub components of a project/features of a project or it can also be used to group the work based on the team that the work will be worked by?

2 answers


Components are project specific, so you would have to create the same components in all projects to be able to use them in a shared board.

From there you can group tasks by components - can use queries to group your tasks in swimlanes. You can write quick filters to view various groupings. You can use components and filters in gadgets.

Not sure what you mean by sub-projects / sub-components, however. What kind of tracking are you trying to do?

0 votes

Hi @Parvathy Manishanker davey 

Can I confirm:

  • Do you have one Jira Project, or multiple?
  • Are the "projects" Epics within one Jira Project?


Components are project-specific - so if you have one Jira project with "projects" as Epics, you could use Components to represent the Team working on each Epic. These can be applied to an Epic's children also.

I'd advise if doing this, give the Team-based Components a prefix, to make them easy to identify (eg. "T:"). I'd do the same with other Components you create, to "group" them together.


If it's 2+ projects, Components wouldn't be my first choice - I'd consider using Labels, Team (if you have Advanced Roadmaps) or a Custom Field instead.

The main reason is Dashboards and Reporting. Whilst 3 projects might have a Component with the same name, they'll still be treated as 3 separate entities on a Dashboard, as they're 3 separate IDs from a back-end database perspective.


Not sure what you mean in terms of your final sentence; could you advise what you are looking to achieve with this grouping?


Suggest an answer

Log in or Sign up to answer
Community showcase
Asked in Jira Service Management

JSM June ask me anything (AMA)

Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...

262 views 13 14
View question

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you