nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Breaking Down Components

GilK

Hi,

We have the following components (few of them, for example):

Mobile Applications

Panel

Peripherals

We have the following sub-components:

Peripherals -> camera

Peripherals -> magnet

Mobile Application -> Android Pegasus

Mobile Application -> BlackBerry Pegasus

Panel -> Protocols

Panel -> Communication

What would be the best way to represent those components and sub-components in JIRA?

Thanks,

Janiv.

Accepted answers

Colin Goudie

Are you a heavy user of Greenhopper?

If you use Greenhopper, setup the components as you have listed them there.

e.g. A components name is "Peripherals - Camera"

This is because Greenhopper only lets you specify one component when editing/creating issues etc..

If you don't use it as much, you can set up each component separately and the user has to multi select Peripherals and also Camera. The upside is you can report on this pretty nice, but downside is you can't force them to only select a combination of components.

You could also create a custom list field to hold one level of the components but there won't be any special relationship between that the component field.

There also was an old multi select cascade CF that may be of interest - https://studio.plugins.atlassian.com/wiki/display/JMLCS/Multi+level+cascade+select

I'd be interested in hearing other solutions too

All comments

Colin Goudie

Are you a heavy user of Greenhopper?

If you use Greenhopper, setup the components as you have listed them there.

e.g. A components name is "Peripherals - Camera"

This is because Greenhopper only lets you specify one component when editing/creating issues etc..

You could also create a custom list field to hold one level of the components but there won't be any special relationship between that the component field.

There also was an old multi select cascade CF that may be of interest - https://studio.plugins.atlassian.com/wiki/display/JMLCS/Multi+level+cascade+select

I'd be interested in hearing other solutions too

GilK

Hi and thank you,

I'm going to use the GreenHooper plugin.

I understand that you can set a single component per issue via GreenHooper. What about JIRA issue? Can I assign an issue few components (for example: a bug that appears in two or more components)?

What do you do with GreenHooper if an issue (say a bug) is relevant for two or more components?

Thanks,

Janiv.

Colin Goudie

What I mean by only one component in greenhopper, is that it is using a single select combo box, so you can't add more than one component to a JIRA issue via greenhopper. If you clieck on the issue so you go to the normal edit JIRA screen then you can command/control click many components to set them on the issue