Index
[Downloads (PDF, HTML & XML formats)]
[Other versions]
Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].
We need to check the following before publishing this page:
You must have the 'JIRA Administrators' global permission to configure GreenHopper's General Configuration settings.
You can configure a number of GreenHopper settings globally (i.e. across all projects in your JIRA instance). A number of these global settings also exist as project settings. Your project settings will override the equivalent global settings.
To configure GreenHopper's global settings,
Please note, all changes made on the General Configuration page are applied immediately.
The general setup options for your project are described below:
To increase the accuracy of the charts you can identify the non-working days for your project (e.g. Saturday and Sunday). These days will simply be withdrawn from the charts. In the case where worklogs are entered in a non working day, these worklogs will be associated to the previous working day to be reflected in the charts. You can enter the non working days that will affect all your JIRA projects from your JIRA Administration Console, i.e. 'Administration' -> 'GreenHopper' -> 'Non Working Days'.
Screenshot: Specifying Non-Working Days Section
To specify non-working days in bulk, edit the time-tracking within JIRA, e.g. if you set JIRA's time-tracking to five days, GreenHopper will take for granted that the weekends are non-working days. Go to 'Administration' > 'Global Settings' > 'Timetracking'. Disable it, change your day settings, then reenable it.
You can also define non-working days specific to a project by clicking the 'Edit' link that appears next to the words 'Non Working Days' at the top of every chart. See Using the Chart Board.
GreenHopper ships with a number of useful listeners and services that can help you maintain the integrity of your GreenHopper data.
To enable listeners and services for GreenHopper,
Screenshot: Registering GreenHopper Listeners and Services Section
You can limit the maximum number of issues displayed on the Task Board to reduce resource consumption. If the number of issues exceeds the specified number, the Task Board will ask the user to narrow the number of issues by using filters from the context.
To limit the maximum number of issues displayed on the Task Board,
Screenshot: Limit GreenHopper's Resource Consumption Section