Note that this page only applies if you are using the Classic Boards
(which are no longer being actively developed; read more
GreenHopper allows you to create parent-child relationships between JIRA components. This allows you to view and track all of the issues assigned to the minor component(s) under the umbrella of a 'parent' component.
All issues under the child component are considered to be a subset of the parent component. These component hierarchies are useful for managing components with many sub-components.
Which component do I see on the cards/summaries?
The component displayed in the summaries and cards is the committed component. If you are using a 'Parent' component, the committed component will be the end-child component where your issue resides. Otherwise, it is simply the component where your issue resides.
To set a component as the parent of another component,
- Log into JIRA.
Select Agile > Classic in the top navigation bar. Then select Classic Planning Board from the drop-down below the project name.
- Select your project from the project dropdown in the top navigation bar, if it is not already selected.
- Change the viewing mode to 'Component' mode.
- Locate the box in the right-hand column for the component that you want to be the child component.
- Edit the Parent field by clicking the icon that will appear when you hover over the field.
- Select the component that you want to be the parent component. The Planning Board will refresh and display your component under its new parent component (see screenshot below). The child component will also have an icon display in its header.
Screenshot: A parent and child component in GreenHopper Classic