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

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 25 Next »

GreenHopper 101

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.

NOTE FROM NICK: What if there are no sortable fields already? See Configuring your General Project Settings. There should likely be a link to create a sortable field and a flag field like there is for Ranking Field when none is present (see http://jira.atlassian.com/browse/GHS-1635 ).

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.

For more help on the technical procedures in this section, see the GreenHopper Installation Guide.

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.

  1. Log in as a user with the 'JIRA Administrators' global permission.
  2. Bring up the JIRA administration page by clicking the 'Administration' menu on the top bar and selecting the 'JIRA Administration' option.
  3. Click the 'GreenHopper Licence' link under the 'System' section of the administration menu. This will display the 'GreenHopper License' screen.
  4. 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.

  • Adding the "Story" issue type:
    *#
    *#
    *#
  • Configuring a card template for the "Story" issue type:
    *#
    *#
    *#

Adding the "Story Point" custom field:
#
#
#

Adding the "Rank" custom field:
#
#
#

  • field needs to be of type "GreenHopper Ranking"? (tbc)

Setting the Planning Board "Context" to sort by Rank:
#
#
#

Setting constraints:
#
#
#

Adding the "Issue Counter" custom field:
#
#
#

The following applies to both Scrum and Kanban.

Adding the "Flag" custom field:
If you configure a "Flag" field, a cautionary image will display on the Task Board behind flagged cards.
#
#
#

Changing the card colours:
#
#
#

Enabling time-tracking:
If you want to be able to log the amount of time you spend working on issues, you need to first do the following:

  1. Click 'Administration' in the top navigation bar.
  2. Click 'Time Tracking' (under 'Global Settings') in the left navigation column.
  3. In the 'Hours Per Day' field, enter the number of hours in your organisation's working day (e.g. 8).
  4. In the 'Days Per Week' field, enter the number of days in your organisation's working week (e.g. 5).
  5. Leave the 'Time Format' as 'pretty'.
  6. Click the 'Activate' button.

For more about configuring time-tracking, please see the JIRA documentation.

Working with Issues

3. Viewing a Project's Backlog

For more information, please see the documentation.

4. Ranking Issues

For more information, please see the documentation.

13. Using Contexts

A Context is a filter that you apply to a board, e.g. enabling you to see only certain cards for a particular version.

5. Scheduling and Assigning Issues

For more information, please see the documentation.

6. Viewing the "To Do" list

For more information, please see the documentation.

7. Transitioning Issues through Statuses

For more information, please see the documentation.

(warning) Note that if moving an issue causes a constraint to be exceeded, the affected column will be displayed in red.

Searching and Reporting

8. Using the Chart Board

For more information, please see the documentation.

9. Using the Released Board

For more information, please see the documentation.

10. Searching for Issues

For more information, please see the documentation.

11. Using the "Agile" Gadget

(MAY NOT BE RELEVANT FOR KANBAN?)

For more information, please see the documentation.

Customising GreenHopper

Note that you need to be a JIRA administrator (OR NOT???) to perform the tasks in this section.

12. Organising Versions and Components

For more information, please see the documentation.

For more information, please see the documentation.

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:

  1. 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.


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.

  • No labels



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.