SUPPORT

You have four different methods to reach us:

1. EMAIL:        GreenHopper Support Team
2. FORUM:      GreenHopper Support Forum
3. JIRA:           GreenHopper's Bug Tracker
4. TWITTER:    https://twitter.com/GreenHopperTeam
   

INSTALL

The installation of GreenHopper is no different from any other JIRA plugin installation.

1. Download the jar file from Downloads (If you have a .zip simply rename your file as a .jar - IE is playing tricks on you)
2. Shut down your Web server.
3. Copy the downloaded jar into your {JIRA_HOME}/atlassian-jira/WEB-INF/lib directory.
   (With a Tomcat, it should be TOMCAT_HOME/webapps/jira/WEB-INF/lib.)
4. Restart your Web server.

To enter your licence go to JIRA --> ADMINISTRATION --> System --> GreenHopper Licence
right under JIRA licence details link

• Click on the new PLANNING BOARD menu tab.
  Note: The last planning board of the last project viewed will be displayed. If there is none, the first project you are allowed to browse will be displayed.

OR

• Browse a project and click the Planning board link.
  
  

GreenHopper does not add or alter JIRA tables or columns. Adding or removing GreenHopper from your installed plugins will not cause any collateral damage to your JIRA data.

UPGRADE

The upgrade of GreenHopper is no different from any other JIRA plugin upgrade.

1. Shut down your Web server.
2. Remove the old version of the jar from your {JIRA_HOME}/WEB-INF/lib directory.
3. Copy the new version of the jar into your {JIRA_HOME}/WEB-INF/lib directory.
4. Restart your Web server.
   
   

   The licence can only be updated by a JIRA administrator.

UNINSTALL

If you really want to uninstall GreenHopper, which we doubt since it is addictive, simply remove the jar from the {JIRA_HOME}/WEB-INF/lib directory. BUT before removing the jar make sure that the GreenHopper Night service is disabled. (JIRA > Administration > Global Settings > GreenHopper >> GreenHopper Listeners and Services >>> GreenHopper night service)

Some TIPS to improve performance

Here is a list that may help you to improve your GreenHopper performance

1. First, make sure your gzip compression from the JIRA > Administration > Global Settings > General configuration is set to on.
2. GreenHopper will play with more then one issue at the same time. Your JVM will then require more Memory then JIRA standalone. We strongly recomment to have at least 512 MB of RAM allocated to your JVM.
3. Since GreenHopper is displaying and building the statistics for all unreleased versions make sure to release your versions once they are done.
4. Use the filters or contexts if you are updating a lot of issues.
5. Avoid adding to much fields in your issue card templates - Remember that all the information needs to travel on the wire...
6. Avoid unlimited text field in your card templates.
7. You can configure your server to add an Expires or a Cache-Control Header
8. If your databse is Postgres please refer to this thread
9. If using Firefox please read this also.
   

Which fix-version or component do I see on the cards/summaries?

The version (or component) displayed in the summaries and cards is the committed version (or component). If you are using the Master option, the committed version (or component) will be the end-child version (or component) where your issue resides. Otherwise, it is simply the version where your issue resides.

Oracle related problems.

Please refer to this page if you are using Oracle with JIRA.

Which fields are required for GreenHopper to be efficient?

The required fields for GreenHopper to be efficient are:

1. The fix version and components, else the planning board would not make any sense.
2. The status of the issue else the task board would not make any sense.
   

Which languages are supported?

For now, English, French, German and Dutch are supported. Almost all character sets (like Cyrillic, Greek...) are supported in the inputs.
More languages will be supported in future releases.

Hierarchy report plugin

The hierarchy plugin can be found here

After the installation, I do not see the Planning Board menu item.

Your version of JIRA might be too old. Sorry, we do not support JIRA 3.6.5 and older. If you do have a supported version, please contact us at: GreenHopper support.

Is the JIRA backup will backup GreenHopper as well?

YES it will BUT you will need to restart your JIRA when restoring a backup since GreenHopper is caching some values and for the restored values to take effect in GreenHopper you will need to empty the cache by restarting your JIRA.

My licence does not seem to work: Uploading => Invalid licence!

Make sure you do not have undesired spaces or carriage returns at the end of your licence after you paste it in the licence box.
To do so, just place your cursor at the end of it (last letter or sign) and press delete a couple of times.

If this didn't work out:

• Make sure your server date is the current date.
• Make sure that if you have a virus checker running to exclude the JIRA install directory and restart the server machine to clear the directory locks.
  Note that TortoiseSVN is another program that has been known to cause the same effect.
  

Difference between the different GreenHopper editions

Some features of JIRA (i.e. sub-tasks, workflow, etc.) are available in higher editions. See JIRA feature comparison.
GreenHopper takes advantage of features like scheduling parents and sub-task at once but to do so your GreenHopper licence has to match your JIRA licence; that is why different editions are available.