Documentation for GreenHopper 5.8.x. Documentation for other versions of JIRA Agile is available too.
GreenHopper is now called JIRA Agile. Learn 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.
- Click the 'Agile' link's down-arrow in the top navigation bar and select 'Planning Board' from the resulting dropdown menu. The 'Planning Board' will be displayed.
- 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
Overview
Content Tools
Apps
Log a request with our support team.
Raise an issue for our developers.
See answers from the community.
Tweet, blog and update our documentation.
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.