Screenshot: Configuring Greenhopper's 'General' Project Settings
Every GreenHopper project has configurations which are derived from a project template. Project templates make it quick and easy to set up and maintain GreenHopper projects with your preferred project configuration settings, which include ranking and flagging fields, card styles and a Task Board mapping.
GreenHopper allows you to choose between two project template settings 'Default' and 'Scrum':
Tip: You have the flexibility to configure the GreenHopper 'Default' template and/or the GreenHopper 'Scrum' template to your organisation's needs — please see the documentation on Specifying your Project Templates. Further, individual projects can override the templates to suit their requirements — please see the sections below on Ranking Fields and Flagging Fields.
If GreenHopper is unable to match configurations from one template to another, for example, as a result of very specific issue type customisations, then a warning message will be displayed.
A ranking field is essentially a GreenHopper-specific custom field that you can use to rank your issues. The ranking field will be made available in the 'Sort by' drop down of your contexts. This will allow you to view your issues ordered by rank and prioritise them by drag and drop.
If you have used the 'Scrum' template, a Ranking Field will be automatically configured for you.
To configure the ranking field for a project (if your project is not using the Scrum template),
Each of your users will now need to go to GreenHopper, edit the Context (or create a new one if necessary), using the Context dropdownand mark it sorted by the Ranking custom field you created. For details, see Ranking Issues in GreenHopper.
Screenshot: Creating a new Context
Screenshot: Sorting the Context by the Ranking custom field
Your users should now be able to drag and drop cards, and the order will adjust the Ranking custom field value.
A flagging field is used in projects to notify of impediments on issues (i.e. you can flag an issue which needs attention). Issues are flagged using a pre-specified value of either a Multi Checkbox or Multi Select custom field, that has been assigned as the flagging field. You can choose which custom field to use as the flagging field and the value that is assigned when an issue is flagged.
If you have used the 'Scrum' template, a Flagging Field will be automatically configured for you.
To configure the flagging field for a project,
If no flagging fields are available for your project,
Read about Flagging an Issue in GreenHopper.
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.
If any non-working days have been specified in GreenHopper's global configuration settings page, then these days will appear in the Non-Working Days sections of all General Project Configuration pages and cannot be deleted.