The planning board is the board that will allow you to manage your issues.
There are three ways to manage your issues:

1. Overview (all unreleased fix versions and unscheduled version merged in one view) Useful for ranking
2. Versions - by unreleased fix versions
3. Components - by components
   

The Manage link will redirect you to the JIRA standard administer project view from where you will be able to add, remove or edit your versions/components.

• The unreleased versions are sorted by release date or JIRA sequence, if none has been defined.
  
  
• This board natural card sorting follows the following rules:
  For performance reasons, if there are more then 200 issues in the selected version and the selected sort is Natural, the issues will be sorted by priority.
  1. Cards are grouped by committed versions, which are sorted by release date/sequence.
  2. Cards with the same committed version are sorted by priority/key.
  3. Sub-tasks are grouped by parent issues.
  4. Sub-tasks of the same parent issue are sorted by priority/key.
     
     

• The components are sorted by name.
  
  
• This board natural card sorting follows the following rules:
  For performance reasons, if there are more then 200 issues in the selected component and the selected sort is Natural, the Issues will be sorted by priority.
  1. Cards are grouped by committed components which are sorted by name.
  2. Cards with the same committed components are sorted by priority/key.
  3. Sub-tasks are grouped by parent issues.
  4. Sub-tasks of the same parent issue are sorted by priority/key.

The main board header offers multiple actions, such as:

1. A version combo to select the version to display
2. Select all | Unselect all multi-selection shortcuts.
3. Pagination that will allow you to navigate between undisplayed issues.
4. Cards | Summaries that will toggle your issue views.
5. List to display issues as a plain old list.
6. Issue navigator that will call the JIRA issue navigator pre-filled with the board parameters displayed.
   Very useful in order to print, make bulk changes, etc.
7. Legend that will show the issue type vs. color legend

• You can define the number of issues to be displayed in the central
  1. board as cards or summaries
     (A high number of issues to display may affect the performance.)
  2. list as rows
• You can decide to view the cards look and feel by default.
• You can define the number of page to be offered in the pagination.
• You can set the refresh rate (in seconds).
• You can set the opacity % of the faded cards for the highlight feature.

With the Master setting in each version/component box, you can organize your versions/components in a n hierarchical way.
This is very useful and will help you have a global view on your versions and a more granular view on your sub-versions.
In the Agile world this will be the way to explode your releases into sprints.

• Example:
  o Version 1
  oo Sub Version 1.1 (Master Version 1)
  oo Sub Version 1.2 (Master Version 1)
  o Version 2
  oo Sub Version 2.1 (Master Version 2)
  ...

When scheduling, your issues will then be updated to the desired version/component and all the master versions/components of this version/component.

• Example:
  If an issue is dropped into Sub Version 1.2
  The issue will then have for fixed versions: Version 1, Sub Version 1.2

In order to help you keep your versions/components hierarchy integrity we have added the Synchronize feature.
This feature will detect all the issues that are missing some versions/components based on your hierarchy.
It will then repair the missing associations.

This feature is only accessible to the project administrators.

You can release your versions directly from the version boxes.
If some issues are unresolved, GreenHoper will offer two options:
    1. Swap the unresolved issues to a the selected version
        After selecting th destination version click on the button
    2. Ignore these issues and release anyways.

GreenHopper will save a snapshot of all your graph before swapping any unresloved issues. You will be able to revisit these charts from the Released charts button in the column header of the fix version boxes.

The issues in GreenHopper can be shown in three different ways:

• The SUMMARY view (default view)
• The CARD view (always accessible by double click on any other views)
• The LIST view
  
  

All these views are configurable by the Project Administrators from the
Planning Board --> Configuration --> CARD pane

1. The templates are by issue types.
2. All added fields will be editable directly from the CARD view.
3. Possibility to add a corner field. (Will be displayed in all views)
4. You can apply a template of a specific issue type to all other issue types by clicking on the Apply to all cards link.
5. You will always be able to re-affect the default templates with the Restore default link for an issue type
6. For each issue types you can also select a color via a very sweet color picker.
   
   

The permission schemes configured in your JIRA are fully respected

Managing your issues between versions and components has actually become a fun task in JIRA with GreenHopper.
By a simple drag and drop you can associate your issues to a fixVersion/component.

The planning board will display all your unreleased fixVersion/components as droppable boxes.
Each of these boxes displays some information such as:

1. Name
2. Master - the parent version/component
3. Release date
4. # of issues by type
5. # of unresolved / resolved issues
6. All the watchable fields (see GreenHopper Fields)
   

Dropping an issue card into the desired version/component box will automatically update the issue version/component. Your version/component information displayed in the boxes will be refreshed.

Since the multi-selection is enabled in the planning board (Alt + left click), to update your selected issues, just drag and drop them into the desired version/component box.

If you are updating a task containing sub-tasks, GreenHopper will automatically ask you if you wish to update the sub-tasks as well. You will be able to choose the ones to update and the ones not to.
Note that the sub-tasks in the same version of the parent will be selected automatically.

With the GreenHopper portlet you can track directly from your dashboard your ongoing versions of your projects.
Multiple shortcuts will allow you to navigate faster.

This protlet can be displayed in confluence with the JIRA portlet macro. Note that you wont be able to access it if your JIRA and Confluence domain differs due to the browser's security for cross domain Ajax calls. In this case you can use the static portlet (see below).