Index
[Downloads (PDF, HTML & XML formats)]
[Other versions]
Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].
データベーステーブル
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'（JIRA Agile 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'
カスタム フィールド
If required, GreenHopper will create the following JIRA custom fields:
| カスタム フィールド | タイプ | 注意 |
|---|---|---|
| 事業価値 | 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 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.
|
| エピック名 | This field is of type 'Label of Epic' (which is a field type created by GreenHopper) and is available to the Epic issue type. | エピック名 (編集可能) はエピックの特定に使用される短い名前です (「エピックの作成」を参照)。 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.
|
| エピック ステータス | 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. エピック ステータス フィールドには次の値のいずれかのみが入ります：
|
| 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. |
| フラグ付き | このフィールドのタイプは「マルチ チェックボックス」タイプです。すべての課題タイプで使用できます。 | See Flagging an Issue (or if you are using the Classic boards, please see Setting up a Flagging Field). |
| ランク | このフィールドのタイプは「グローバル ランクルチ チェックボックス」です。すべての課題タイプで使用できます。 | 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). JIRA インスタンスには、ランクというカスタムフィールドが1つしかなく、そのランクフィールドはグローバル·コンテキストに割り当てられている (すなわち、特定の課題やプロジェクトには割り当てられていない) ことを確認してください。
|
| 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 | このフィールドのタイプは「スプリント」です。すべての課題タイプで使用できます。 | Searchable via JQL. This field was introduced in GreenHopper 5.8.5. It does not apply to the Classic Boards.
|
| ストーリーポイント | このフィールドのタイプは「数字」であり、「ストーリー」および「エピック」で使用できます。 |
|
This field is not configurable via the 課題タイプ
At installation time, GreenHopper will create the following three JIRA issue types and associate them with the Default 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:
- 「バグ」
- 「エピック」
- 「改善点」
- 「ストーリー」
- 「技術タスク」 (サブタスク)
You can add more issue types to this issue type scheme if you wish (provided you have 'JIRA Administrators' global permission).
ワークフロー
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.
| 簡易ワークフロー | JIRA ワークフロー |
|---|---|
Has three default steps for Scrum boards: To Do, In Progress, Done. 4 つの カンバンボード用の既定手順：バックログ、開発選択、進行中、完了 | Has more steps than are typically needed on a board (e.g. see the default JIRA workflow). |
| 列間で課題を自由にドラッグできる | 課題がすべての列間で自由にドラッグされないようにするワークフロー "条件" がある。 |
トランジション時に画面を表示しない – すべてのトランジションは即座に実行される。 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. |
権限
Many GreenHopper actions depend on a particular JIRA permission:
| 機能 | モード | 操作 | 許可レベル | 注意 |
|---|---|---|---|---|
| スプリント | Plan | スプリント マーカーを動かす | Project Admin Permission (for all projects in the backlog) | |
| スプリント | Plan | 課題を動かす (並べ替え/ランク) | Schedule Permission | 課題の順序を変更せずにスプリントのフッター内で課題を動かすだけの場合は不要 |
| スプリント | Plan | スプリントの開始 | Project Admin Permission (for all projects where an issue is in the selection) | バージョンを作成する同様の権限。ボード所有権はここでは役割を果たしません。 |
| スプリント | Plan | スプリントの作成 | Project Admin Permission:
| |
| スプリント | Plan | スプリントの削除 | Project Admin Permission:
| |
| スプリント | Plan/Work | スプリントに課題を追加する | Issue Edit Permission | |
| スプリント | Plan | スプリント情報の編集 | Project Admin Permission (for all issues in the sprint) | Currently only accessible via Plan mode |
| スプリント | Work | スプリントの完了 | JIRA 管理者またはスプリントのすべての課題のプロジェクト管理者 | Can only be done from Work mode. |
| スプリント | Work | スプリントから削除 | 課題の編集権限 | |
| エピック | Plan | エピックの作成 | 課題の作成権限 | (Epics launched out of Labs in 6.1) |
| エピック | Plan | エピックの名前の変更 | 課題の編集権限 | |
| エピック | Plan | エピックのランク付け | 課題のスケジュール設定権限 | |
| エピック | Plan | 課題をエピックへ追加する | 課題の編集権限 | |
| エピック | Plan | エピックから課題を削除する | 課題の編集権限 | |
| バージョン | Plan | バージョンの作成 | プロジェクト管理者権限、または JIRA 管理者権限 | (6.2 の Labe から立ち上げられたバージョン) |
| バージョン | Plan | バージョンの編集 | プロジェクト管理者権限、または JIRA 管理者権限 | |
| バージョン | Plan | バージョンに課題を追加する | 課題の編集権限 | |
| バージョン | Plan | バージョンから課題を削除する | 課題の編集権限 | |
| Config | Configure | ワークフローを簡素化 | Administrator Permission | ボードもその他の条件を満たす必要があります (「ワークフローの簡素化」を参照) |
| Config | Configure | ステータスの追加 | Project Admin Permission (for the one project that is on the board) | Project must be currently using a GreenHopper Simplified Workflow |
| Config | Configure | ステータスの削除 | Project Admin Permission (for the one project that is on the board) | Project must be currently using a GreenHopper Simplified Workflow |
| Config | ボードの作成 | 共有オブジェクトの作成グローバル権限 | この権限を持っていなくても、ボードは作成できますが、作成したボードのフィルタが共有されないため、他の人にはボードが表示されません。 現在コピーボードに適用されていない |
サンプル データ
On the GreenHopper "Getting Started" page you have the option of importing sample data. If you choose to do this, GreenHopper will:
- JIRA Importers アドオンを更新します。
- 「Scrum サンプル」および「Kanban サンプル」という 2 つのサンプルプロジェクト (選択した場合はこれらの名前を変更できます)、およびそれらの課題をインポートします。
- これらのプロジェクトそれぞれに対して「簡易ワークフロー」または「簡易ワークフロースキーム」を作成します (上記を参照)。
あとでこれらのプロジェクト、ワークフローおよびワークフロースキームを削除できます。また、これらのスクリプトを使用して、同様のサンプルデータを後でインポートすることもできます。
概要
コンテンツ ツール
アプリ
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
Dec 09, 2011how 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
Apr 05, 2012is 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
Aug 04, 2012Hi,
I am looking to do the same thing as described above by the two users
thanks
Anonymous
Oct 04, 2012No 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]
Oct 09, 2012Please see Configuring the Issue Detail View
Andrew Ardill
Oct 10, 2012What 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]
Oct 30, 2012The "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
Oct 29, 2012Sprint 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]
Oct 30, 2012You may like to watch/vote/comment on GHS-4949 - Getting issue details... STATUS
Anonymous
Oct 31, 2012We 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
Dec 14, 2012Is it possible to move the sprints up or down on the planning board?
Rosie Jameson [Atlassian]
Dec 16, 2012You may like to watch/vote/comment on GHS-6131 - Getting issue details... STATUS
Anonymous
Jan 09, 2013How 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]
Jan 13, 2013Coming soon. Please watch our Release Notes.
Anonymous
Jan 10, 2013Simple 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
Jan 28, 2013Please 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)
Feb 28, 2013We would like to remove greenhopper and all configuration items from the configuration.
What's the best approach ?
Rosie Jameson [Atlassian]
Feb 28, 2013After 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
Mar 11, 2013What 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
Mar 11, 2013And using the Classic Migration came up with no Epics to migrate. ???
Rosie Jameson [Atlassian]
Mar 11, 2013Can you please contact http://support.atlassian.com ? Many thanks
MattS
Apr 04, 2013This 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]
Apr 15, 2013Thanks 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
Apr 05, 2013for me these fields are insta;;ing 3 times
Rosie Jameson [Atlassian]
Apr 07, 2013Can you please contact http://support.atlassian.com ? Thank you
Pilar Cantarero
Apr 09, 2013Hi,
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]
Apr 10, 2013Can you please contact http://support.atlassian.com ?
MattD
Apr 23, 2013Create Sprint may be grayed out if your board filter has not had ranking reenabled after you updated it.
MattS
Jul 16, 2013I have found that sometimes if the board filter is not ordering by Rank then Sprints cannot be created.
MattS
Jul 16, 2013So I found the same thing out twice. Sounds like the docs need updating!
MattS
Aug 08, 2013It 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.