I. GreenHopper Global Configuration
GreenHopper Default Configuration Pane
GreenHopper has now a default configuration that will be applied to all new JIRA projects.
All JIRA administrators will be able to access this pane from the Administration - Global Settings.
Restrict GreenHopper to Specific Projects
You can select the projects that will be allowed to use the GreenHopper plugin.
TaskBoard Resources
You can limit the number of issues to show in the TaskBoard thus limiting resource consumption.
If the number of issues exceeds the specified number, the TaskBoard will ask the user to narrow the number of issues by using filters from the context.
This feature was added to support Public or Open source projects to avoid undesired resource load on the server.
General Set Up
Each projects can override this setting through the Planning Board -> Configuration -> GENERAL
- You can override the fix version editing permission (Resolve Issues) with the JIRA Schedule issues permission.
The user will then need the Schedule Issues permission to drag and drop card into version boxes.
- You can choose to use your own JIRA look and feel or the GreenHopper look and feel.
- You can decide to use a modal screen for the issue views. This option will help you view or create issues without loosing your planning board focus. Very useful
- If you have the link-hirearchy-plugin installed you can select the issue link type to branch GreenHopper to.
Issue Views Configuration
Each projects can override this setting through the Planning Board -> Configuration -> CARDS
- To harmonize your projects you can configure a default set of color for your cards.
TaskBoard Column Mapping
Each projects can override this setting through the Planning Board -> Configuration -> TASK BOARD
For each column of your TaskBoard you can associate multiple JIRA Statuses AND multiple JIRA Resolutions. Based on your workflow and your TaskBoard mapping, GreenHopper will present to the users the available workflow actions when dragging a card from a column to another. If the workflow screen of your workflow step asks for the "Resolution", users will also be able to select the Resolution to set the issue in.
Important: The TaskBoard column "DONE" is the owner of your Project's "Done Definition". GreenHopper will rely on this definition to burn your values in the charts and to swap issues on version releases.
Warning: Playing with the resolutions can be very hazardous. If you are not comfortable with the JIRA Workflows and Workflow screens, We advise you to leave the resolution settings to "ANY".
III. Non Working Days
|
To increase the accuracy of the charts we have decided to support the non working days. 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 to enter non working days to be affected to all your JIRA projects from your JIRA -> Administration -> GreenHopper ---> Non Working Days.
You can also define non working days specific to a project. See ChartBoard header |
IV. GreenHopper Fields
- Sorted Fields
You can add sortable custom fields in the Sort by combo box in the context menu
|
|
- Flagging Fields
You can flag an issue based on a multi checkboxes or select custom field value.
You will need to create a custom field (Multi checkboxes or select) and associate options:
| Multi checkboxes |
Multi select |
Select the label of the checkbox to base your flagging on. - Flagging your Issue will check the issue label. - Unflagging your Issue will uncheck the issue label. |
Select the option of the multi select to base your flagging on. - Flagging your Issue will add the option to your Issue selected options. - Unflagging your Issue will remove the option from your Issue selected options. |
|
|
- Ranking Fields
See Issue ordering from the planning board configuration.
The rank of an issue can be set:
- By drag and drop directly from the planning board (The context has to be sorted by this field).
- Within the standard Issue view of JIRA if the screen is selected.
- Within the standard Issue update view of JIRA if the screen is selected.
|
|
|