Assigning Subcomponents to Issues

First, the Subcomponent-Component Versions custom field must be created and assigned to the relevant screens.

Open

If you want to configure the custom field, you can go to the configuration page of the custom field itself and select the version columns you want to see in the custom field or you can select the option to override the version fields. For more information on configuring the custom field, you can click here.

Open

If you want you can add a “Subcomponent-Component Version Custom Field” to an issue. This will allow you to select a different set of Project Components for the issue. This field works exactly like the built-in Project Component field with the addition of a subcomponent picker for selecting components from the hierarchy. This field can coexist with the built-in Project Components field. For more information on selecting component versions of the Project Component, you can click here.

After creating the issue, you can go to the issue's view screen and see the version hierarchy according to which subcomponent is selected in the relevant custom field section, the selected subcomponent, and its versions in column order. For example, in this configured custom field, only the information of the Affects version should be seen. The hierarchy is shown as follows: pathOfSubcomponent/selectedAffectVersion. Another example is if Hardware versions were also selected, then the hierarchy would look like this: pathOfSubcomponent/selectedAffectVersion/selectedHardwareVersion.

You can also press the view screen unselect the components selected in the relevant custom field and select new components or versions.