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
@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
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