Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

Is There any way to create "Sub-Component" for a Project..?

Is There any way to create "Sub-Component" for a Project under a component (like a dependent component)

3 answers

That's not possible jira does not support hierarchical components, in my previous organization we used cascading select field to achieve this, we created a two level cascading select field first option list is same as component names but hidden by javascript, on component on change method set the value in first level which will automatically update options at second level.

i would like to assign default assignee for each items in the cascading select field first option list.

Is this Possible..?

I don't think that's possible by minor tweaks, as you would also need a place where you can define the assignment based on subcomponents IMHO it would be a lot of work to get it right, won't be possible by tweaking javascript.

if you're looking to assign to sub-components, short of a lot of coding work, I'd just use the components and use structured text to imply a kind of hierarchy...

MyMajorComponent-FirstSubComponent - Assignee=User1

MyMajorComponent-SecondSubComponent - Assignee=User2

MyOtherComponent-FirstSubComponent - Assignee=User3

It's less than perfect but it's workable

@MatthewC this is the approach I'm taking for managing Component hierarchy. I'm trying to minimize the use of Jira plugins and complexity.

@MatthewC  Can you please give more pointers on what exactly you did to add sub components. (where do I start?) 

@Joseph Philip all we're talking about here is to create your own naming convention that you use for Components field, with major/minor component levels separated by a delimiter (as @Matthew Cobby illustrated), and then search/parse/interpret the Components field accordingly in your workflows. In Matthew's example above, since:




are all distinct Components from Jira's perspective, they each have their own "Lead" as he's also indicated.

The main issue with this approach is in the reports. if you want to slice a chart based on components, there will be too much sliced because each component is split to at least 2. This issue is pretty massive, jira is complex but this basic functionality doesn't exist.. bummer

Not really I'm afraid.. or I just didn't find the correct way.

This addon doesn't appear as a field so you can't access it from the "open issue" screen.. thisis pretty useless I hope they'll get back to me I sent a ticket

Like eugenia_matushchenko likes this

Suggest an answer

Log in or Sign up to answer

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