Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].

(info) 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,

  1. Log into JIRA.
  2. Select Agile > Classic in the top navigation bar. Then select Classic Planning Board from the drop-down below the project name.
  3. Select your project from the project dropdown in the top navigation bar, if it is not already selected.
  4. Change the viewing mode to 'Component' mode.
  5. Locate the box in the right-hand column for the component that you want to be the child component.
  6. Edit the Parent field by clicking the icon that will appear when you hover over the field.
  7. 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

9 Comments

  1. Anonymous

    Sept 21, 2011

    Hi,

    I have created a hierarchy of components for my project and it works ok. But now i have an issue because I would like to select multiple components when adding a sub-task and I am not allowed to do that from the Greenhopper view (+New Card). Did anyone found a solution for this? I am forced to use the "Create Issue" screen that takes a lot more time.

    Thanks,

    Bogdan

  2. Anonymous

    Feb 03, 2012

    How do you use the component parent in JQL?  I want to filter on all items where the component's parent component is "X" and not have to include all of the sub components (which are many and can change)

  3. Karie Kelly

    Sept 06, 2012

    Having the same issue with parent/child versioning. How do we use JQL or reporting to be able to utilize this functionality? We would like to have high level components of integration, configuration, planning with sub components.  But, if the querying, gadgets, and rapid boards don't also support, I cannot see the value in utilizing.  Can someone provide guidance on how to gain value from the feature?

  4. Ed Gonzales

    Jan 15, 2013

    Is this possible functionality with Greenhopper v5.8.7 running on JIRA v4.4.4?

    1. Ed Gonzales

      Jan 15, 2013

      nvm, I got it (smile)

      Another question - when performing a JQL search, is it possible to only search the parent component and generate results that include the children components?

      1. Rosie Jameson [Atlassian]

        Jan 15, 2013

        Not as such. The component-nesting functionality is unique to GreenHopper.

        1. Ed Gonzales

          Jan 15, 2013

          Thanks Rosie! So the parent-child functionality in Greenhopper is merely for reporting/viewing purposes?

  5. Ed Gonzales

    Mar 06, 2013

    Comment removed

  6. Gregory Demotchkine

    Aug 05, 2013

    Basically a parent component is just like a regular component, so in effect only GreenHopper knows their relationship. 

    Using the Classics boards, this does present a few advantages....

    In terms of assigning, what actually happens or rather should happen, is that your users should continue to assign their issue to the childen components (unless they are motivated to select the parent and the child and know the relationship betwen all parent-child by heart since JIRA component drown menu is still a flat list)  

    What greenHopper does is when you click on Tools\Synchronise (while being on the (Classic planning boards) it actually detects that your Parent Component is missing from all of the children component assigned issues (if that's the case) and proposes to add the parent just like a regular component alongside the child component. So when you go to the issue or try searching with JQL you can perfectly find all of your issues using the parent or child criteria .. or a mix.. 

    Hopefully this clarifies things a bit. 

    My question is how do I have an automatic synchronization between GreenHopper and JIRA or is there one already? if latter, how do I specify how often it's triggered? (i.e every hour ) 
     

     

     

     

     

     

     

     



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.