Relationship between Issues and Components

[Dave Wilcox]

Right now, our JIRA is broken out by Business Unit = Project.  Then, we have Issue Types.  We cannot filter the Components by Issue type though.  We see ALL Components for each Issue Type.  It would be good if we could filter Components by issue type.  For example, if we have a Software setup issue, we would see components of (Office, JIRA Access, etc).  If use selects Issue = Report Request, then they would see components of (Report Type 1, Report Type 2, etc. ).  As it is, regardless of the Issue Type, they see ALL components.  So, a user that selects Software Setup, will see ALL components --> Office, JIRA Access, Report Type 1, Report Type 2.  Maybe we have a flawed setup??  This seems odd.  

[Nic Brough -Adaptavist-]

Yes, that is designed behaviour.  A component is a project artefact, not an issue type thing.

I don't like agreeing with the phrase "flawed setup", it's a bit too negative, it's more like you've got a need for certain data structures and you've accidentally chosen the wrong way to do it.

You can do "component/s by issue type" with a custom field instead.  If you add a "multi-select list" field, you can give it a different list of options by issue type.

 But, if you do this, you do not get the functionality of component/s - the options have to be maintained by JIRA admins (not project), there's no component lead, and the built-in reporting ill still refer to components.  You will need to make a call as to whether those are acceptable.  Note that there are a couple of addons that bypass the "only JIRA admins" issue, so you should look at those before ruling it out.