Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].

In Work mode, a board displays vertical columns. By default, each board contains three columns, called 'To Do', 'In Progress' and 'Done'. You can add, delete, rename or move these columns if you wish. You can also choose which JIRA workflow status(es) each column is mapped to, and whether any constraints apply to each column.

(info) Note that only the owner of a board (or a person with the 'JIRA Administrators' global permission) can configure a board's columns.

列を編集する

ボードの列を編集する手順は、次のとおりです:

  1. Select Agile > Manage Boards from the top navigation bar, then click the Configure link corresponding to the board of interest.
  2. タブをクリックします。

  3. Edit the columns as described in the following table and Screenshot 1 (below).

    編集項目

    操作方法

    新規列の追加

    ページの右側にある列の追加ボタンをクリックします。「新しい列」という名前の新規の列が、最後から 2 番目の列の位置に追加されます。

    (info) If you are using Simplified Workflow, then a new status will automatically be created to match your new column.

    列の名前の変更

    列の名前エリアをクリックして、既存の名前を変更し、エンターキーを押します 。

    列の削除

    Click the trash-can icon at the top-right of the column.
    (info) Any JIRA workflow statuses that had been mapped to the deleted column are moved back to the 'Unmapped' column.

    列の移動

    Hover over the horizontal 'grid' icon, then drag the column left or right to its new position. Wait until other columns have shifted position before dropping the selected column to its new position.

 

Screenshot 1: the 'Board Configuration' screen — 'Columns' tab.

(info) The number in brackets after the status name shows the number of issues currently in that status.

列を JIRA ステータスにマッピングする

By default, a board's columns are mapped to the default JIRA statuses as shown in the following tables. You can change this if you wish. For example, if you are using additional, customised JIRA statuses, you will probably want to map them to appropriate columns in your board.

If your board's project is using the JIRA default workflow:

既定の列既定でマッピングされた JIRA ステータス
作業前オープン、再オープン
進行中進行中
完了解決済み、クローズ

 ・・・または・・

ボードのプロジェクトで簡易ワークフローを使用している場合

既定の列既定でマッピングされた JIRA ステータス
作業前作業前
進行中進行中
完了完了

  


JIRA ワークフロー ステータスとボード上の列のマッピングを編集する手順は、次のとおりです:

  1. Select Agile > Manage Boards from the top navigation bar, then click the Configure link corresponding to the board of interest.
  2. タブをクリックします。

  3. 次の表とスクリーンショット 1 (上) に示すように、ステータスのマッピングを変更します。

    編集項目

    操作方法

    ステータスを列にマッピングする

    ステータスをマッピングなし列から右側の該当する列にドラッグします。

    ステータスと列のマッピングを削除する

    ステータスを、右側の現在の列から左側のマッピングなし列にドラッグします。

    ステータスと列のマッピングを変更する

    ステータスを、元の列から該当の新しい列にドラッグします。

    (info) All statuses configured in the JIRA server are available from the board Configuration page. However, some statuses (in particular, custom statuses) may not be available for issues on your board if the JIRA workflow(s) used by these issues do not utilise those statuses.

 

(tick) See the Tutorial - Adding a Column to a Board for an example of creating a new column and mapping it to a new JIRA status.

 

新規のステータスを追加する

If your board is using Simplified Workflow:

  1. Select Agile > Manage Boards from the top navigation bar, then click the Configure link corresponding to the board of interest.
  2. タブをクリックします。

  3. Click the Add Status button at the right of the page.
    (info) Note that the Add Status button is only available if you have the JIRA 'Project Administrator' permission for this board's project.

簡易ワークフローをボードで使用していない場合は、チュートリアル - ボードへの列の追加の手順にしたがってください。

 

ステータスを削除する

If your board is using Simplified Workflow:

  1. Select Agile > Manage Boards from the top navigation bar, then click the Configure link corresponding to the board of interest.
  2. タブをクリックします。

  3. ステータスをマッピングなし列にドラッグします。

  4. Click the delete icon (trash can) for the status you wish to remove.
    (info) Note: that you can only delete a status if you have the JIRA 'Project Administrator' permission for this board's project.
    (info) You can only delete a status if there are no issues that currently have that status.
    (info) If any other workflows are using this status then the status will be removed from your workflow, but not deleted.

If your board is not using Simplified Workflow, you can only delete a status vis the JIRA administration interface — please see the JIRA documentation on Configuring Workflow.

 

列の制約の設定

制約は、列に含めることができる課題の数を指定します。制約をかけるのは、すべての列か、または一部の列だけか指定できます。

サブタスクをカウントから除外する選択が可能です。この選択が便利なのは、個々のタスクの総数よりも、チームが取り組んでいる主要なタスク(ストーリー)の数を制約する場合です。この制約の方法は、カンバンチームよりもスクラムチームに関係が深いと思われます。

To set 'Maximum' and 'Minimumum' constraints for a column of a board:

  1. Select Agile > Manage Boards from the top navigation bar, then click the Configure link corresponding to the board of interest.
  2. タブをクリックします。

  3. 次の表とスクリーンショット 1 (上) に示すように、制約を編集します。

    編集項目

    操作方法

    列の制約を有効にする
    In the Column Constraint drop-down, select either Issue Count or, if you don't want to include sub-tasks in the column count, Issue Count, excluding sub-tasks.
    列の「最小値」の制約を設定する

    列の上部にある黄色のボックスをクリックして、新しい値を入力し、エンターキーを押します。

    列の「最大値」の制約を設定する

    列の上部にある赤色のボックスをクリックして、新しい値を入力し、エンターキーを押します。

    列の「最小値」の制約を削除する

    列の上部にある黄色のボックスをクリックして、現在の値を削除し、エンターキーを押します。

    列の「最大値」の制約を削除する

    列の上部にある赤色のボックスをクリックして、現在の値を削除し、エンターキーを押します。

    すべての列の制約を削除する
    列制約ドロップダウンから、なしを選択します。

 

 

26 Comments

  1. Anonymous

    Is it possible to use other constraint in place of Issue Count?

  2. Anonymous

    I would also like to use another constraint. Issue Count is not suitable if the "size" of the issues is very different. For example the estimated amount of work would be much more helpful.

    My proposal: Any number-typed field should be possible to be used as constraint.

    1. Please watch/vote/comment on GHS-4917 - Getting issue details... STATUS

  3. Zach Leber

    In GH 6.0.3 I see "Release..." in grey next to my Done column header but we use our Kanban board to track continuous issue resolution so don't have any releases.  Can the release link be hidden?

     

    1. This issue may be helpful? GHS-6676 - Authenticate to see issue details

  4. Anonymous

    I created a KanBan board. Is there a way to show estimate or remaining time on the cards on the board?

  5. Anonymous

    Is there a way to create limits by user (or by row)? For example, create limit so a certain user can not have more tan x number of issues in progress status. The only way I could find to use this is to create swimlanes but I do not get an alert when the limit is broken as it happens with the limits by columns.

    I think it would be useful to allow the configuration of limits by users (or by rows).

  6. Anonymous

    It seems it is only possible to have multiple columns for 'In progress'. 'Done' and 'Todo' is always the rightmost and leftmost column.

    I think there is a need to be able to track activity in more detail in the Done and Todo field. E g if I have a workflow that is: Reported -> Assigned -> In progress -> Done. I would like to have both Reported and Assigned as 'Todo'. 

    r

    1. You should be able to achieve this by renaming the leftmost column, then adding other columns as needed.

      If I have misunderstood your requirements, please accept my apologies and contact http://support.atlassian.com who will be able to assist further.

  7. Anonymous

    I would like to change the field each column is based on from issue type to some other field however the board is not allowing me to do so.  Is there a way to change the field the columns are based on?

  8. Anonymous

    When dragging between columns, how does GH know which status to use if there are multiple statuses mapped to a column?

    1. You will be prompted to choose the applicable status – please see Transitioning an Issue

  9. MattS

    What do the colors of the columns mean when adding columns?

    • Red = left-most column
    • Green = right-most column
    • Yellow = all other columns

    Do these colors appear on the actual board anywhere, or just in the configuration?

    1. They only appear in the configuration

      1. MattS

        So, no significance to the colors beyond first and last columns?

        1. Correct, no significance (on the new boards)

          1. Maxwell Zierath

            Hey Rosie, it looks to me like the Velocity Chart will only use issues that are within the status mapped to the green column for tracking velocity.

            For instance, mapped a confirm resolve status to the green column, and put the closed in the yellow. When looking at the velocity chart that way, the team's overall velocity was only calculated by issues in the confirm resolve status and the ones that were closed did not affect velocity.

            Is there any way to add in more than one column as a completed column?

            1. The Velocity Chart shows sprints that have been completed

  10. Andrew Fisher

    Is it possible to change the default "JIRA workflow to column" mapping?  I know that I can change each board's mapping individually by doing into the board's config, but I want to define a slightly different column mapping, and then have that be used as the default mapping on any new board that is then set up. Thanks!

    1. MattS

      I'd like that too, plus changing the default columns. I haven't seen a Feature Request for it at jira.atlassian.com yet?

    2. Daniel Guerra

      I am interested in this as well, I have over 10 projects and I don't want to have to customize the board for each one.  I want to use a standard template

      1. Maxwell Zierath

        Same - we've got 20+ boards due to the number of projects and teams we have. Even though setting one up takes 10-15m tops, it would be nice to set a default.

  11. Cedric Burns

    I want to constrain the WIP by estimated task hours rather than by number of tasks. Any ideas about how to do this (except by some averaging scheme?)

  12. Zuzana Hriniková

    I want to hide/show columns when needed without having several boards - is it possible?

    Use case: We have several steps (eg. "ready for code review", "code review in progress", "ready for testing", "is being tested" etc.) in our workflow, each status is mapped to the separate column. Tester usually doesn't want to see columns "code review" and "code review in progress" he/she only wants to see "ready for testing" and "is being tested" columns. Developer usually wants to see the other columns. There are situation when both need to see all columns. We do not want to have several boards for the same project.

    1. MattS

      This would be very useful. A Quick Filter will hide all the issues, but the column is still there. How about an option to not show a column if it's empty?

      1. Zuzana Hriniková

        It would be wonderful if it could work the same way as you can show/hide swimlanes by clicking on the arrow.