Welcome to GreenHopper 101, an introductory guide to the GreenHopper plugin for JIRA and a tour of the most interesting GreenHopper features. Use this page to guide your evaluation process or quickly get up to speed with GreenHopper.
Software developers are the intended audience for this document.
Getting Started
1. Installing GreenHopper
First things first. If you haven't already got the GreenHopper plugin up and running, carry out the following steps:
*Before you begin:*If you don't already have JIRA 4.0 or later installed, please follow the instructions in the JIRA Installation and Upgrade Guide.
Unable to render {include} The included page could not be found.
It should only take you a few minutes to install the GreenHoppper plugin. If you have any difficulty during the installation process, please contact our support team for assistance. They're ready to help at any time.
Bring up the JIRA administration page by clicking the 'Administration' menu on the top bar and selecting the 'JIRA Administration' option.
Click the 'GreenHopper Licence' link under the 'System' section of the administration menu. This will display the 'GreenHopper License' screen.
Enter your license details and click 'Add'.
GreenHopper license must match JIRA license
Please note, if you are using a commercial (i.e. not an evaluation) license for GreenHopper, it must match your JIRA license. For example, if you have a JIRA 25 User Commercial license you must have a GreenHopper 25 User Commercial license. GreenHopper evaluation licenses do not need to match JIRA licenses.
2. Configuring JIRA and GreenHopper
Note that you need to be a JIRA administrator to perform the tasks in this section.
field needs to be of type "GreenHopper Ranking"? (tbc)
Note that GreenHopper supports only one Fix Version per issue. If an issue is assigned to multiple versions, GreenHopper will only use the first one in the list. It is recommended that you:
Edit each issue
Note that GreenHopper supports only one component per issue, so if an issue belongs to multiple components, GreenHopper will only use the first one in the list. (Note: components are listed alphabetically, so if there are three components selected — "cats", "dogs", "planes" — it will only use 'cats'.)
In agile programming, if a task/issue is so broad that it covers many components, it should be broken down into smaller tasks.
13. Using Contexts
Do we need this as well as the Contexts item in "2. Configuring GreenHopper and JIRA"?
Thank you for reading this guide.
Thanks for taking the time to try GreenHopper using this guide. To help continue your journey, our support staff are always ready to answer your questions in the GreenHopper Forum, or solve specific problems at our support portal http://support.atlassian.com.