Index
[Downloads (PDF, HTML & XML formats)]
[Other versions]
Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].
Database tables
When you install the GreenHopper add-on 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 the Epic issue type. | 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 the Epic issue type. | 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 the Epic issue type. | 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. | See Flagging an Issue (or if you are using 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' and is available to issue types 'Story' and 'Epic'. |
|
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 are transitioned to the desired statuses (choose the desired statuses by ticking the checkbox next to the status when configuring the board's columns).
| 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 | Create version | Project Admin permission, or JIRA Admin permission | (Versions launched out of Labe in 6.2) |
| Versions | Plan | Edit version | Project Admin permission, or JIRA Admin permission | |
| Versions | Plan | Add issue to version | Edit Issues permission | |
| Versions | Plan | Remove issue from version | Edit Issues permission | |
| Config | Configure | Simplify workflow | Administrator Permission | The board must meet other criteria as well (see Simplified Workflow) |
| Config | Configure | Add status | Project Admin Permission (for the one project that is on the board) | Project must be currently using a GreenHopper Simplified Workflow |
| Config | Configure | Remove status | Project Admin Permission (for the one project that is on the board) | Project must be currently using a GreenHopper 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 add-on.
- 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.
31 Comments
Anonymous
how to add my own customefield in green hooper card
i want to add issuePicker customefield in new card of green hooper , but i unable to retrieve drop down list it mens all issue
can any beady help me please
Anonymous
is it possible to add other issue types, like 'task' to the 'GreenHopper Scrum Issue Type Scheme'? and if I do so, do i miss something of Greenhoppers functionality ?
Anonymous
Hi,
I am looking to do the same thing as described above by the two users
thanks
Anonymous
No responses yet? I just signed up for this product but it's kinda useless to me without being able to add fields to the cards/columns. We rank based on certain field values, summary does us no good.
Rosie Jameson [Atlassian]
Please see Configuring the Issue Detail View
Andrew Ardill
What are the restrictions on who has access to GreenHopper's functionality?
It seems like there is some 'magic' requiring a user to be a member of the group 'jira-users' before they can see user options regarding GreenHopper. They can still see the Agile menu item but are missing the down arrow and nested options (such as switching to classic view or looking at the other boards available) and instead are directed to the 'Getting Started' page whenever they click on this menu item. Such a user can still navigate to boards they have access to by entering the URL manually or following link, and can even configure them, but they cannot search for or add new boards.
This seems like something that should be using a (global?) permission instead of a group, but if it is indeed hard-coded to a group then it should be documented somewhere (here!).
Rosie Jameson [Atlassian]
The "JIRA Users" global permission is required to log in to JIRA and GreenHopper. By default this permission is granted to the group "jira-users", but you can use a different group if you wish. For more details please see the JIRA documentation on Managing Global Permissions.
Anonymous
Sprint is a searchable field but only as a numeric. Our current sprint is labelled 3.34.0, but I can only see these by searching for sprint = 11. How can i search for sprint based on the descriptions we assign to a sprint?
Rosie Jameson [Atlassian]
You may like to watch/vote/comment on GHS-4949 - Getting issue details... STATUS
Anonymous
We have an established project with 2 custom workflows already in place that deal with specific issue types. When we try to use greenhopper (new edition to our project) we can't see anything in the backlog, or other greenhopper screens relating to our project. Will greenhopper not work with more than 1 workflow, that are both completely custom?
Anonymous
Is it possible to move the sprints up or down on the planning board?
Rosie Jameson [Atlassian]
You may like to watch/vote/comment on GHS-6131 - Getting issue details... STATUS
Anonymous
How do I search for issues associated with a given epic? Ideally by epic name but I'd settle for by the epic ticket #.
Rosie Jameson [Atlassian]
Coming soon. Please watch our Release Notes.
Anonymous
Simple group chart allow to make grouping only by Epic Status
Will be wonderful to make epic name available too at least. Other wise a lot of dashboards will be unusable.
Anonymous
Please can you advise why I cannot move a Story from To Do to In Progress but I can move the sub-story of that Story.
Hilde Van Brempt (Atlassian)
We would like to remove greenhopper and all configuration items from the configuration.
What's the best approach ?
Rosie Jameson [Atlassian]
After removing the GreenHopper plugin, you would need to manually delete the fields and issue types, and also delete the AO tables from the database. Please contact http://support.atlassian.com if you need assistance with this.
Dave Sokolowski
What steps are necessary to move from using Epic/Theme to all of the new Epic fields? Should we be putting all the new fields on the JIRA screens? And then bulk editing any of the current Epics? Not sure on what the recommended course of action here is. Thanks!
Dave Sokolowski
And using the Classic Migration came up with no Epics to migrate. ???
Rosie Jameson [Atlassian]
Can you please contact http://support.atlassian.com ? Many thanks
MattS
This page would be a good starting place for some GreenHopper Developer documentation that explains the underlying model of how GreenHopper works. For example, a sprint doesn't belong to a board. An issue has a sprint and all boards that select that issue with their filters will see that sprint.
Rosie Jameson [Atlassian]
Thanks for the suggestion, that's a great idea. I will try to schedule some time for that when things quieten down a bit (and also, there are some upcoming changes to the data model so it would be best to wait till after those).
If you have suggestions for specific information you'd like to see on such a page, could you please add a comment to this issue? GHS-8450 - Getting issue details... STATUS
Thanks again.
jim blizzard
for me these fields are insta;;ing 3 times
Rosie Jameson [Atlassian]
Can you please contact http://support.atlassian.com ? Thank you
Pilar Cantarero
Hi,
We have detected a bug since the Epic Name is now a non-editable field. We never use epics in our projects, for now this has not been a problem, but in the new plugin version, this field is required and moreover it cannot be edited from settings screen. So, in our case, the field name now applies to a specific issue type (not to all) and this behavior seems random… Any way to have this field configurable in order not to apply to our issue types?
Thanks in advance!
Rosie Jameson [Atlassian]
Can you please contact http://support.atlassian.com ?
MattD
Create Sprint may be grayed out if your board filter has not had ranking reenabled after you updated it.
MattS
I have found that sometimes if the board filter is not ordering by Rank then Sprints cannot be created.
MattS
So I found the same thing out twice. Sounds like the docs need updating!
MattS
It seems that in 6.2.5.1 if I have deleted the Epic/Theme field because I'm not using Classic GH, then GH will not recreate the field when GH is updated. This is a good thing.