GreenHopper JIRA Configuration

データベーステーブル

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'（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'

On this page:

関連ページ

カスタムフィールド

If required, GreenHopper will create the following JIRA custom fields:

カスタムフィールド	タイプ	注意
エピックの色	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, and is only created if 'Epics' is enabled in Labs. 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 all issue types.	Epic Label (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, and is only created if 'Epics' is enabled in Labs. 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, and is only created if 'Epics' is enabled in Labs. 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 all issue types.	Not currently used. It is intended that Epic Status will eventually be used to exclude completed epics from being displayed. This field was introduced in GreenHopper 6.0.6, and is only created if 'Epics' is enabled in Labs. 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.
フラグ付き	このフィールドのタイプは「マルチチェックボックス」タイプです。すべての課題タイプで使用できます。	This field only applies to 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つしかなく、そのランクフィールドはグローバル·コンテキストに割り当てられている (すなわち、特定の課題やプロジェクトには割り当てられていない) ことを確認してください。
ストーリーポイント	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 '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.)
GreenHopper Released Version History	This field is of type 'Multi Version Field' 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.

課題タイプ

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 'GreenHopper Simplified Workflow for Project XXX' (see Configuring Workflow), and a workflow scheme called 'GreenHopper 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.

GreenHopper Simplified Workflow	JIRA ワークフロー
Has three default steps: To Do, In Progress, Done.	Has more steps than are typically needed on a board (e.g. see the default JIRA workflow).
列間で課題を自由にドラッグできる	課題がすべての列間で自由にドラッグされないようにするワークフロー "条件" がある。
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.

権限

GreenHopper uses the following JIRA permissions:

操作	権限	注意
Login to JIRA and GreenHopper	'JIRA Users' global permission
Move Sprint Footer (Plan mode)	'Administer Projects' permission (for all projects in the backlog)
Move Issue (reorder/rank) (Plan mode)	'Schedule Issues' permission	課題の順序を変更せずにスプリントのフッター内で課題を動かすだけの場合は不要
Start Sprint (Plan mode)	'Administer Projects' permission (for all projects where an issue is in the selection)	バージョンを作成する同様の権限。ボード所有権はここでは役割を果たしません。
Add Issue to Sprint (Plan mode and Work mode)	'Edit Issues' permission
Remove Issue from Sprint (Plan mode and Work mode)	'Edit Issues' permission
Edit Sprint Information (Plan mode)	'Administer Projects' permission (for all issues in the sprint)	Currently only accessible via Plan mode
Complete Sprint (Work mode)	'JIRA Administrators' global permission, or 'Administer Projects' permission for all issues in the sprint
Simplify Workflow (Board configuration)	'JIRA Administrators' global permission	The board must meet other criteria as well
Add Status (Board configuration)	'Administer Projects' permission (for the one project that is on the board)	Project must be currently using a GreenHopper Simplified Workflow
Remove Status (Board configuration)	'Administer Projects' permission (for the one project that is on the board)	Project must be currently using a GreenHopper Simplified Workflow
Create Board with Shared Filter	'Create Shared Objects' global permission	この権限を持っていなくても、ボードは作成できますが、作成したボードのフィルタが共有されないため、他の人にはボードが表示されません。

サンプルデータ

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.
「Scrum サンプル」および「Kanban サンプル」という 2 つのサンプルプロジェクト (選択した場合はこれらの名前を変更できます)、およびそれらの課題をインポートします。
Create a "GreenHopper Simplified Workflow" and a "GreenHopper 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.

Child pages