Documentation for GreenHopper 6.1.x. Documentation for other versions of JIRA Agile is available too.
GreenHopper is now called JIRA Agile. Learn more.
Database tables
When you install the GreenHopper plugin into your JIRA instance, the following additional tables will be created in your JIRA database to store rank, configuration and sprint information:
- 'AO_60DB71_COLUMN'
- 'AO_60DB71_COLUMNSTATUS'
- 'AO_60DB71_ESTIMATESTATISTIC' (added around 5.9.5)
- 'AO_60DB71_ISSUERANKING'
- 'AO_60DB71_ISSUERANKINGLOG'
- 'AO_60DB71_QUICKFILTER'
- 'AO_60DB71_RANK_ISSUE_LINK'
- 'AO_60DB71_RAPIDVIEW'
- 'AO_60DB71_SPRINT'
- 'AO_60DB71_STATSFIELD'
- 'AO_60DB71_SUBQUERY'
- 'AO_60DB71_SWIMLANE'
- 'AO_60DB71_TRACKINGSTATISTIC'
Custom fields
If required, GreenHopper will create the following JIRA custom fields:
| Custom field | Type | Notes |
|---|---|---|
| Business Value | This field is of type 'Number Field' and is available to issue types 'Story' and 'Epic'. (If you want to make it available to other issue types, edit the custom field context.) | |
| Epic Colour | This field is of type 'Colour of Epic' (which is a field type created by GreenHopper) and is available to all issue types. | Epic Colour is the colour assigned to the epic. This is auto-assigned initially then can be changed via a dropdown on the colour box on the epic (in GreenHopper 6.0.7 and later). This field was introduced in GreenHopper 6.0.6. It does not apply to the Classic Boards.
|
| Epic Name | This field is of type 'Label of Epic' (which is a field type created by GreenHopper) and is available to all issue types. | Epic Name (editable) is a short name that is used to identify an epic (see Creating an Epic). This field was introduced in GreenHopper 6.0.6. It does not apply to the Classic Boards.
|
| Epic Link | This field is of type 'Epic Link Relationship' (which is a field type created by GreenHopper) and is available to all issue types. | Epic Link is used to determine the parent epic for an issue. This is a non-editable field; it is set by GreenHopper when you add/remove an issue to/from an epic. Searchable via JQL. This field was introduced in GreenHopper 6.0.6. It does not apply to the Classic Boards.
|
| Epic Status | This field is of type 'Status of Epic' (which is a field type created by GreenHopper) and is available to all issue types. | Epic Status is used to exclude completed epics from being displayed in Plan mode. This field was introduced in GreenHopper 6.0.6. It does not apply to the Classic Boards. The Epic Status field can have one of the following values:
|
| Epic/Theme | This field is of type 'Label' and is available to all issue types | This field only applies to the Classic Boards. Please see Working with Epics in GreenHopper Classic. |
| Flagged | This field is of type 'Multi Checkboxes' and is available to all issue types. | This field only applies to the Classic Boards. Please see Setting up a Flagging Field. |
| Rank | This field is of type 'Global Rank' and is available to all issue types. | See also Enabling Ranking (or if you are using the Classic Planning Board then see Setting up a Ranking Field and Specifying your Project Templates). Please ensure that your JIRA instance contains only one custom field called Rank, and that the Rank field is assigned to the global context (i.e. not to specific issues or projects).
|
| Release Version History | This field is of type 'GreenHopper Released Version History' and is available to all issue types. | This field only applies to the Classic Boards. |
| Sprint | This field is of type 'Sprint' and is available to all issue types. | Searchable via JQL. This field was introduced in GreenHopper 5.8.5. It does not apply to the Classic Boards.
|
| Story Points | This field is of type 'Number Field' and is available to issue types 'Story' and 'Epic'. (If you want to make it available to other issue types, edit the custom field context.) |
This field is not configurable via the Issue types
At installation time, GreenHopper will create the following three JIRA issue types and associate them with the Default Issue Type Scheme:
- 'Epic'
- 'Story'
- 'Technical Task' (sub-task)
Issue type scheme
At installation time, GreenHopper will create a new issue type scheme called 'GreenHopper Scrum Issue Type Scheme' which contains the following issue types:
- 'Bug'
- 'Epic'
- 'Improvement'
- 'Story'
- 'Technical Task' (sub-task)
You can add more issue types to this issue type scheme if you wish (provided you have 'JIRA Administrators' global permission).
Workflow
If you choose to create a new project when creating a board via the 'Getting Started' page, GreenHopper will give you the option of creating a new workflow called 'Simplified Workflow for Project XXX' (see Configuring Workflow), and a workflow scheme called 'Simplified Workflow Scheme for Project XXX' for your new project. This scheme is associated with all issue types.
Note that this workflow's steps can be edited in GreenHopper (by project administrators) via a board's Columns configuration page. For more information please see Using GreenHopper Simplified Workflow.
| Simplified Workflow | JIRA Workflow |
|---|---|
Has three default steps for Scrum boards: To Do, In Progress, Done. Has four default steps for Kanban boards: Backlog, Selected for Development, In Progress, Done. | Has more steps than are typically needed on a board (e.g. see the default JIRA workflow). |
| Allows issues to be dragged freely between columns. | Has workflow "conditions" which prevent issues from being dragged freely between all columns. |
Displays no screens on any transitions – all transitions will happen instantly. (Automatically sets a resolution of 'Done' when issues move into the 'Done' column.)
| Displays screens for Resolve Issue, Close Issue and Reopen Issue. |
| Can be edited from within GreenHopper (see Adding a new status on the Configuring Columns page), provided you have the 'Administer Projects' permission (for the one project that is on the board). | Can only be edited via JIRA (see Configuring Workflow), not from within GreenHopper. |
Permissions
Many GreenHopper actions depend on a particular JIRA permission:
| Feature | Mode | Action | Permission Level | Notes |
|---|---|---|---|---|
| Sprints | Plan | Move sprint marker | Project Admin Permission (for all projects in the backlog) | |
| Sprints | Plan | Move issue (reorder/rank) | Schedule Permission | Not required if you only move issues across the sprint footer without changing the order of the issues |
| Sprints | Plan | Start sprint | Project Admin Permission (for all projects where an issue is in the selection) | Similar permission to creating a Version. Board ownership does not play a role here. |
| Sprints | Plan | Create sprint | Project Admin Permission:
| |
| Sprints | Plan | Delete sprint | Project Admin Permission:
| |
| Sprints | Plan/Work | Add issue to sprint | Issue Edit Permission | |
| Sprints | Plan | Edit sprint information | Project Admin Permission (for all issues in the sprint) | Currently only accessible via Plan mode |
| Sprints | Work | Complete sprint | JIRA Administrator or Project Admin for all issues in the sprint | Can only be done from Work mode. |
| Sprints | Work | Remove issue from sprint | Edit Issues permission | |
| Epics | Plan | Create epic | Create Issues permission | (Epics launched out of Labs in 6.1) |
| Epics | Plan | Rename epic | Edit Issues permission | |
| Epics | Plan | Rank epic | Schedule Issues permission | |
| Epics | Plan | Add issue to epic | Edit Issues permission | |
| Epics | Plan | Remove issue from epic | Edit Issues permission | |
| Versions | Plan | Add issue to version | Edit Issues permission | (Versions added to Labs in 6.1.4) |
| Versions | Plan | Remove issue from version | Edit Issues permission | |
| Config | Configure | Simplify workflow | Administrator Permission | The board must meet other criteria as well (see GreenHopper Simplified Workflow) |
| Config | Configure | Add status | Project Admin Permission (for the one project that is on the board) | Project must be currently using a Simplified Workflow |
| Config | Configure | Remove status | Project Admin Permission (for the one project that is on the board) | Project must be currently using a Simplified Workflow |
| Config | Create board | Create Shared Objects global permission | People without this permission can still create boards but they will not be visible to other users of the system because their filter will not be shared. Doesn't currently apply to Copy Board. |
Sample data
On the GreenHopper "Getting Started" page you have the option of importing sample data. If you choose to do this, GreenHopper will:
- Update the JIRA Importers Plugin.
- Import two sample projects, called "Scrum Sample" and "Kanban Sample" (you can rename these if you choose), and their issues.
- Create a "Simplified Workflow" and a "Simplified Workflow Scheme" (see above) for each of these projects.
You may want to delete these projects, and their workflows and workflow schemes, at a later date. You can also use these scripts to import similar sample data later on.
Overview
Content Tools
Apps
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.