將資料行加入至您的儀表板面板Add columns to your Kanban board

Azure Boards |Azure DevOps Server 2020 |Azure DevOps Server 2019 |TFS 2018-TFS 2013Azure Boards | Azure DevOps Server 2020 | Azure DevOps Server 2019 | TFS 2018 - TFS 2013

看看的第一種作法是將工作流程視覺化。Kanban's number one practice is to visualize the flow of work. 因此,您的第一個工作是將小組的工作流程視覺化。Accordingly, your number one task is to visualize your team's workflow. 您可以藉由找出小組將專案從待處理專案移出待處理的狀態時,定期執行這項工作,以執行這項工作。You perform this task by identifying the types of work and hand-offs that occur regularly as your team moves items off the backlog and into a shippable state.

例如,我們的範例開發小組所執行的主要工作流程階段,會在此被視為分析、開發和測試。For example, the main workflow stages performed by our example dev team are captured here as Analyze, Develop, and Test. 每個資料行都對應至小組在每個專案上執行的工作階段,然後才能將它視為完成。Each column corresponds to a work stage the team performs on each item before it can be considered done.

看板,已自訂資料行Kanban board, columns customized

找出小組的工作流程階段之後,您就可以將您的儀錶 板面板設定為對應After you identify your team's workflow stages, you're ready to configure your Kanban board to map to them. 一旦設定之後,您就可以使用您的儀表板面板來更新狀態、重新指派工作,以及重新排序專案,以反映變更的優先順序。Once configured, you use your Kanban board to update status, reassign work, and reorder items to reflect changing priorities.

如果您剛開始使用,請參閱 看看看看的基本概念 ,以瞭解如何存取您的電路板和執行的儀表板。If you're just getting started, review Kanban basics to get an overview of how to access your board and implement Kanban.

注意

如果您要瞭解如何將資料行加入至短期衝刺工作面板,請參閱 自訂工作面板If you're looking at how to add columns to a sprint Taskboard, see Customize a Taskboard. 若要將資料行加入至待處理專案或查詢結果,請參閱 變更資料行選項To add columns to a backlog or query results, see Change column options.

注意

如果您要瞭解如何將資料行新增至工作面板,您需要自訂工作流程。If you're looking at how to add columns to a taskboard, you need to customize the workflow. 如需詳細資訊,請參閱 加入或修改工作專案類型For details, see Add or modify a work item type. 若要將資料行加入至待處理專案或查詢結果,請參閱 變更資料行選項To add columns to a backlog or query results, see Change column options.

如需每個待處理專案和麵板上所支援功能的總覽,請參閱待處理專案 、面板和方案視圖For an overview of the features supported on each backlog and board, see Backlog, board, and plan views.

為何要設定您的儀表板面板資料行?Why configure your Kanban board columns?

設定小組的看板面板資料行的主要原因,是為了支援您小組的工作流程和處理常式。The main reason to configure your team's Kanban board columns is to support your team's workflow and Kanban processes. 這些程式可能會在認可工作之前包含分級工作、管理從某個小組成員到另一個小組成員的移交, — 例如進行開發以測試 — 管理進行中的工作 (WIP) 等等。These processes may include triaging work prior to committing to the work, managing handoff from one team member to another—such as development to test—managing Work in Progress (WIP), and more.

此外,您可以使用您的看板面板來執行下列工作:In addition, you can use your Kanban board to perform the following tasks:

必要條件Prerequisites

  • 您必須有想要設定的一種儀表板面板。You must have a Kanban board you want to configure. 當您加入小組時,您會加入該小組的儀表板面板。When you add a team, you add a Kanban board for that team. 若要深入瞭解,請參閱 關於小組和 Agile 工具To learn more, see About teams and Agile tools.
  • 若要設定小組設定,您必須將設定為 [小組系統管理員] 角色或 [ Project Administrators ] 安全性群組的成員。To configure team settings, you must be added to the team administrator role or be a member of the Project Administrators security group. 若要加入,請參閱 加入小組系統管理員設定專案或集合層級的許可權To get added, see Add a team administrator or Set permissions at the project- or collection-level.
  • 指派 基本 存取權或更高版本的使用者,可以執行所有待處理專案和麵板功能。Users assigned Basic access or higher can exercise all backlog and board features.
  • 使用者指派的專案關係 存取權對待處理專案和麵板功能具有有限的存取權。Users assigned Stakeholder access have limited access to backlog and board features. 專案關係人可以編輯面板上的工作專案,並將現有的標記加入至工作專案。Stakeholders can edit work items on the board and add existing tags to a work item. 他們無法將工作專案加入至面板,也無法更新卡片上顯示的欄位。They can't add work items to a board and can't update fields displayed on cards. 如需詳細資訊,請參閱 關於存取層級For details, see About access levels.
  • 您必須有想要設定的一種儀表板面板。You must have a Kanban board you want to configure. 當您加入小組時,您會加入該小組的儀表板面板。When you add a team, you add a Kanban board for that team. 若要深入瞭解,請參閱 關於小組和 Agile 工具To learn more, see About teams and Agile tools.
  • 若要設定小組設定,您必須將設定為 [小組系統管理員] 角色或 [ Project Administrators ] 安全性群組的成員。To configure team settings, you must be added to the team administrator role or be a member of the Project Administrators security group. 若要加入,請參閱 加入小組系統管理員設定專案或集合層級的許可權To get added, see Add a team administrator or Set permissions at the project- or collection-level.
  • 指派 基本 存取權或更高版本的使用者,可以執行所有待處理專案和麵板功能。Users assigned Basic access or higher can exercise all backlog and board features.
  • 使用者指派的專案關係 存取權對待處理專案和麵板功能具有有限的存取權。Users assigned Stakeholder access have limited access to backlog and board features. 專案關係人可以編輯面板上的工作專案,並將現有的標記加入至工作專案。Stakeholders can edit work items on the board and add existing tags to a work item. 他們無法將工作專案加入至面板、無法拖放工作專案來更新狀態或重新排列卡片,也無法更新卡片上顯示的欄位。They can't add work items to a board, can't drag-and-drop work items to update status or reorder cards, and can't update fields displayed on cards. 如需詳細資訊,請參閱 關於存取層級For details, see About access levels.

此外,我們建議您複習下列文章:In addition, we recommend that you review the following articles:

面板資料行自訂序列Board column customization sequence

設定小組的 [儀表板] 面板資料行之前,您會想要確定已盡可能完成下列工作。Before you configure your team's Kanban board columns, you'll want to make sure the following tasks are complete as possible. 否則,您會發現自己已重新取得您的設定。Otherwise, you'll find yourself revisiting your configuration. 重新整理單一小組的設定是一件事,不過如果您支援許多團隊,則可以略過此步驟來新增額外的工作。Revisiting a single team's configuration is one thing, however if you support many teams, then you've added extra work by skipping this step.

進程管理員Process Administrator:

  1. 新增您想要顯示在待處理專案或面板上的自訂工作專案類型。Add custom work item types that you want to appear on your backlog or board. 如需詳細資訊,請參閱 加入和管理工作專案類型For details, see Add and manage work item types.
  2. 自訂您的產品和待辦專案組合,以確保您想要擁有的所有工作專案類型都會出現在待處理專案和麵板上。Customize your product and portfolio backlogs to ensure all work item types you want to have will appear on the backlogs and boards. 如需詳細資訊,請參閱 自訂待處理專案 & 面板。For details see Customize backlogs & boards.
  3. 自訂工作流程狀態。Customize workflow states. 每個工作流程狀態都會顯示為儀表板上的資料行。Each workflow state appears as a column on the Kanban board. 如需詳細資訊,請參閱 自訂工作流程For details, see Customize a workflow

小組系統管理員Team Administrator:

  1. 為您的小組設定要使用的待處理專案(backlog)。Set the backlogs you want active for your team. 您只需要設定您的小組將會使用之待處理專案的工作面板。You only need to configure the Kanban boards of those backlogs that your team will use. 如需詳細資訊,請參閱 為您的小組選取待處理專案導覽層級For details, see Select backlog navigation levels for your team.
  2. 判斷 bug 的追蹤方式。Determine how bugs will be tracked. Bug 可能與其他需求工作專案類型的工作流程狀態不同,因此必須與其他工作專案類型分開對應。Bugs may have different workflow states from other requirement work item types and therefore must be mapped separate from other work item types. 如需詳細資訊,請參閱在待處理專案 和麵板上顯示 bugFor details, see Show bugs on backlogs and boards.
  3. 識別您的小組將用來支援其工作流程和處理板程式的資料行。Identify the columns your team will use to support their workflow and Kanban processes. 如需詳細資訊,請參閱本文稍後 的「對應工作流程 」。For details, see Map the flow of work later in this article.
  4. 加入、移除或重新命名資料行,並將工作流程狀態對應到資料行。Add, remove, or rename columns and map workflow states to columns. 如需詳細資訊,請參閱本文稍後的 加入、編輯、重新命名或移除資料行、分割資料行For details, see Add, edit, rename, or remove columns, split columns later in this article.

例如,如果您加入 bug 或其他工作專案類型,使其出現在儀表板上,您可能會引進其他工作流程狀態。For example, if you add bugs or other work item types to appear on a Kanban board, you potentially introduce other workflow states. 當您進行下列其中一項自訂時,新的工作流程狀態會要求您調整看板資料行 狀態 對應:New workflow states request you to adjust the Kanban column State mappings when one of the following customizations is made:

什麼是狀態對應?What is State mapping?

若要正確地將資料行加入至您的儀表板,您需要瞭解的其中一個主要設定詳細資料,是工作流程狀態如何對應至儀表板面板的資料行狀態。One of the main configuration details you need to understand to correctly add columns to your Kanban board is how workflow states map to Kanban board column states. [儀表板] 和其他 Azure 面板工具會使用類別來分組要視為相同的 Wit。The Kanban board and other Azure Board tools use categories to group WITs that they want to treat the same. 使用兩種類型的類別。Two types of categories are used.

  • 工作專案類型分類Work item type categories:

    • 只有其工作專案類型屬於需求分類的工作專案才會顯示在產品面板上。Only work items whose work item types belong to the Requirement Category show up on the product board.
    • 只有工作專案類型屬於功能分類的工作專案才會顯示在功能組合面板上。Only work items whose work item types belong to the Feature Category show up on the Feature portfolio board.
    • 只有工作專案類型屬於長篇故事分類的工作專案才會顯示在長篇的組合面板上。Only work items whose work item types belong to the Epic Category show up on the Epic portfolio board.
    • 只有屬於自訂分類之工作專案類型的工作專案才會顯示在自訂的公事包面板上。Only work items whose work item types belong to a custom category show up on a custom portfolio board.
  • 狀態類別State categories:

    • 有四個以上的狀態類別:「已 建議」、「 進行中」、「 已完成」及「 已移除」。There are four and only four state categories: Proposed, In Progress, Completed, and Removed.
    • 針對工作專案類型定義的工作流程狀態屬於四種狀態類別的其中一種。Workflow states defined for a work item type belong to one of the four state categories.
    • 針對每個工作專案類型和每個儀表板面板資料行,必須指定工作流程狀態 (但 已移除 類別) 中的工作流程狀態除外。For each work item type and each Kanban board column, the workflow state must be specified (except those workflow states in the Removed category).
    • 第一個 [儀表板面板] 資料行會自動對應到每個工作專案類型的 [ 建議 的狀態] 類別的預設狀態。The first Kanban board column is automatically mapped to the default State for each work item type's Proposed state category.
    • 若為中間的看板面板資料行,您可以將資料行對應至任何屬於「 建議 」或「 進行中 」狀態類別的狀態。For middle Kanban board columns, you can map the column to any of the states that belong to the Proposed or In Progress state categories. 此外,您只能針對這些資料行指定 進行中的工作限制分割資料行,以及 完成的定義Also, you can only specify Work in Progress limits, Split columns, and Definition of Done for these columns.
    • [ 已完成 ] 狀態類別目錄只能對應到最後一個 [儀表板] 面板資料行。The Completed state category can only map to the last Kanban board column.

提示

如果工作流程狀態未對應到 [查看] 資料行,則該狀態不會顯示在 [儀表板] 面板上。If a workflow state isn't mapped to a Kanban column, then that state doesn't show up on the Kanban board. 這是允許的,但不建議使用。This is allowed but not recommended.

修正您的儀表板面板設定Correct your Kanban Board configuration

如果您在開啟儀表板面板時看到下列錯誤,則需要更正設定。If you see the following error when you open your Kanban board, you need to correct the configuration. 此錯誤的主要原因是,已加入至需求分類的工作專案類型工作流程狀態未對應到資料行。The main reason for this error is that the workflow states of work item types that have been added to the Requirements category aren't mapped to the column.

儀表板,設定錯誤訊息Kanban board, Configuration error message

選擇 [ 立即更正 ] 以開啟 [ 設定 ] 對話方塊。Choose Correct this now to open the Settings dialog.

在此範例中,已加入兩個新的狀態,並針對 bug 進行 分級,並****調查 使用者案例。In this example two new states have been added, Triaged for bug, and Investigate for user story. 每個狀態都必須對應到現有或新的資料行,以便讓看板面板顯示指派給這些狀態的工作專案。Each state needs to be mapped to an existing or new column in order for the Kanban board to display work items assigned to these states.

Kanban board settings, Columns

TFS 2015.1 在此範例中,已加入兩個新的狀態,並針對 bug 進行 分級,並****調查 使用者案例。TFS 2015.1 In this example two new states have been added, Triaged for bug, and Investigate for user story. 每個狀態都必須對應到現有或新的資料行,以便讓看板面板顯示指派給這些狀態的工作專案。Each state needs to be mapped to an existing or new column in order for the Kanban board to display work items assigned to these states.

Kanban board settings, Columns

TFS 2015 在此範例中,已加入 bug,以顯示在儀表板面板上。TFS 2015 In this example, bugs have been added to show on the Kanban board. 您需要在看板上對應每個資料行的 bug 狀態。You need to map the bug state for each column on the Kanban board.

看板狀態對應的資料行 (含 Bug)Kanban column to State mappings with bugs

在此範例中,已加入 bug,以顯示在儀表板面板上。In this example, bugs have been added to show on the Kanban board. 您需要在看板上對應每個資料行的 bug 狀態。You need to map the bug state for each column on the Kanban board.

看板狀態對應的資料行 (含 Bug)Kanban column to State mappings with bugs

對應工作流程Map the flow of work

如果您想要讓整個團隊找出一組初始的工作流程階段,最好是如此。It's best if you involve the entire team to identify an initial set of workflow stages. 每個小組成員都提供實用的觀點,讓小組瞭解端對端程式更加深入。Each team member provides useful perspectives to capture and further deepen team understanding of the end-to-end processes.

若要開始使用,請向您的小組詢問下列問題:To get started, ask your team these questions:

  • 我們會定期執行哪些類型的活動?What types of activities do we regularly perform?
  • 我們的團隊內會發生什麼自然的?或者,從我們的團隊到其他團隊呢?What natural hand offs occur within our team? Or, from our team to other teams?
  • 哪些活動將有助於強化我們的小群組原則,例如分析、程式碼審核或設計接受?What activities will help reinforce our team policies, such as analysis, code review, or design acceptance?
  • 每個階段需要執行什麼工作?What work needs to occur at each stage?
  • 我們想要為每個工作流程狀態設定哪些限制?What limits do we want to set for each workflow state?
  • 分割資料行是否適用于一或多個資料行?Will a split column be useful for one or more columns?

我們的範例開發小組將這些階段視為其程式的必要專案:Our example development team came up with these stages as essential to their process:

範例工作流程階段Example workflow stages

  • 處理專案:尚未準備好處理的工作專案優先順序清單Backlog: Prioritized list of work items that aren't yet ready to work on
  • 分析:已識別清楚且共用的接受準則和開發和測試專案所需的整體工作Analyze: Well understood and shared acceptance criteria identified and overall work required to develop and test item
  • 開發:程式碼並執行專案的單元測試Develop: Code and run unit tests for the item
  • 測試:執行探索、自動化、整合和其他測試Test: Perform exploratory, automated, integration, and other tests
  • 完成:專案已準備好交付至生產環境。Done: Item ready to handoff to production.

您稍後可以隨時重新流覽這些初始階段並進行調整。You can always revisit these initial stages later and adjust.

另一項構想是,捕捉您的小組在每個階段都能完成的重要專案清單。Another idea, capture the list of items your team identifies as critical-to-complete for each stage. 您稍後可以使用該資訊來填寫針對每個資料行所 做的定義You can use that information later to fill out the Definition of Done for each column.

新增、編輯、重新命名或移除資料行Add, edit, rename, or remove columns,

現在您已瞭解如何使用您的儀表板面板,以下是讓它看起來像您需要的方式。Now that you've got the essentials of how to work with your Kanban board, here's how you get it to look like what you need it to.

您將會根據用來建立 專案的程式 ,以及您的小組是否選擇將 bug (例如需求或類似工作)視為不同的資料行標題和選擇。You'll see different column titles and choices based on the Process you used to create your project and whether your team has chosen to treat bugs like requirements or like tasks.

  1. 開啟您的看板面板Open your Kanban board. 如果您不是小組系統管理員,請 加入成為一個系統管理員。If you're not a team admin, get added as one. 只有 team 和 project admins 可以自訂該儀表板。Only team and project admins can customize the Kanban board.

  2. 選擇 [設定 小組設定] 以設定面板並設定 [一般小組] 設定。

    開啟小組的面板設定,垂直導覽Open board settings for a team, vert nav

  3. 選擇 [資料 ],然後選擇 [資料行] 索引標籤,以查看您可以修改的所有設定。Choose Columns and then a column tab to see all the settings you can modify. 您的初始資料行設定看起來會像下圖所示的設定。Your initial column settings look similar to the settings shown in the following image.

    設定對話方塊、資料行、使用中資料行、Agile 流程。Settings dialog, Columns, Active column, Agile process.

  4. 變更您的資料行標題,以對應至您的工作流程階段。Change your column titles to map to your workflow stages. 您可以新增、重新命名和移動資料行,以支援更多階段。You can add, rename, and move columns to support more stages.

    在這裡,我們會將第一個、第二個和第三個數據行重新命名為待處理專案、分析和開發。Here, we rename the first, second, and third columns to Backlog, Analyze, and Develop. 接著,我們會新增資料行並標示其測試。We then add a column and label it Test.

    您可以直接從儀表板面板重新命名資料行。You can rename a column directly from the Kanban board.

    Kanban board, rename a column directly

    或者,您可以開啟對話方塊,並變更一個或多個「查看板」資料行的設定。Or, you can open the dialog and change one or more settings for a Kanban column.

    設定、資料行、新增和重新命名資料行、Agile 流程Settings, Columns, Add and rename columns, Agile process

  5. 若要變更資料行順序,請將 [資料行] 索引標籤拖曳至您想要的位置。To change the column order, drag the column tab to the position you want.

  6. 若要刪除資料行,請先確認資料行未包含任何工作專案。To delete a column, first make sure that the column doesn't contain any work items. 如果有的話,請將專案移到另一個資料行。If it does, move the items to another column. 然後,開啟 [ 設定],選擇 [資料 ],然後從 [資料行] 索引標籤選擇 [動作] 圖示,然後從功能表選取 [ 移除 ]

    設定對話方塊、資料行索引標籤、開啟資料行索引標籤功能表、移除資料行Settings dialog, Columns tab, open Column tab menu, remove column

  7. 視需要變更 新增的資料行、新增的工作流程狀態,或新增工作專案類型 (wit) 所需的狀態對應。Change State mappings as needed for added columns, added workflow states, or added work item types (WITs).

    當您變更 [使用 bug ] 設定、將 Wit 加入至需求分類,或 自訂工作流程時,通常需要更新 狀態 對應。Usually you need update State mappings when you change the Working with bugs setting, add WITs to the Requirement Category, or customize the workflow.

  8. 完成變更之後,請選擇 [ 儲存]。When done with your changes, choose Save.

  1. 開啟您的看板面板Open your Kanban board. 如果您不是小組系統管理員,請 加入成為一個系統管理員。If you're not a team admin, get added as one. 只有 team 和 project admins 可以自訂該儀表板。Only team and project admins can customize the Kanban board.

  2. ChooseChoose 設定圖示 開啟 [儀表板] 的 [一般設定] 對話方塊。to open the common configuration settings dialog for the Kanban board.

    [儀表板],開啟一般設定

  3. 選擇 [資料 ],然後選擇 [資料行] 索引標籤,以查看您可以修改的所有設定。Choose Columns and then a column tab to see all the settings you can modify. 您的初始資料行設定看起來會像這樣。Your initial column settings will look something like this.

    設定對話方塊、自訂資料行、預設資料行、Agile 流程。Settings dialog, Customize columns, default columns, Agile process.

  4. 變更您的資料行標題,以對應至您的工作流程階段。Change your column titles to map to your workflow stages. 您可以新增、重新命名和移動資料行,以支援更多階段。You can add, rename, and move columns to support more stages.

    在這裡,我們會將第一個、第二個和第三個數據行重新命名為待處理專案、分析和開發。Here, we rename the first, second, and third columns to Backlog, Analyze, and Develop. 接著,我們會新增資料行並標示其測試。We then add a column and label it Test.

    您可以直接從儀表板面板重新命名資料行。You can rename a column directly from the Kanban board.

    Kanban board, rename a column directly

    或者,您可以開啟對話方塊,並變更一個或多個「查看板」資料行的設定。Or, you can open the dialog and change one or more settings for a Kanban column.

    Kanban board, Settings, Columns, Add and rename  columns, Agile process
  5. 若要變更資料行順序,請將 [資料行] 索引標籤拖曳至您想要的位置。To change the column order, drag the column tab to the position you want.

  6. 若要刪除資料行,請先確認資料行未包含任何工作專案。To delete a column, first make sure that the column doesn't contain any work items. 如果有的話,請將專案移到另一個資料行。If it does, move the items to another column. 然後,選擇 [資料行] 索引標籤 動作圖示,然後從功能表中選取 [ 移除 ]。

    將資料行刪除的儀表板面板Kanban board, delete a column

  7. 視需要變更 新增的資料行、新增的工作流程狀態,或新增工作專案類型 (wit) 所需的狀態對應。Change State mappings as needed for added columns, added workflow states, or added work item types (WITs).

    當您變更 [使用 bug ] 設定、將 Wit 加入至需求分類,或 自訂工作流程時,通常需要更新 狀態 對應。Usually you need to update State mappings when you change the Working with bugs setting, add WITs to the Requirement Category, or customize the workflow.

  8. 完成變更之後,請選擇 [ 儲存]。When done with your changes, choose Save.

  1. 開啟您的看板面板Open your Kanban board. 如果您不是小組系統管理員,請 加入成為一個系統管理員。If you're not a team admin, get added as one. 只有 team 和 project admins 可以自訂該儀表板。Only team and project admins can customize the Kanban board.

  2. ChooseChoose 設定圖示 開啟 [儀表板] 的 [一般設定] 對話方塊。to open the common configuration settings dialog for the Kanban board.

    [儀表板],開啟一般設定

  3. 選擇 [資料 ],然後選擇 [資料行] 索引標籤,以查看您可以修改的所有設定。Choose Columns and then a column tab to see all the settings you can modify. 您的初始資料行設定看起來會像這樣。Your initial column settings will look something like this.

    看板、自訂資料行、預設資料行、Agile 流程

  4. 變更您的資料行標題,以對應至您的工作流程階段。Change your column titles to map to your workflow stages. 您可以新增、重新命名和移動資料行,以支援更多階段。You can add, rename, and move columns to support more stages.

    在這裡,我們會將第一個、第二個和第三個數據行重新命名為待處理專案、分析和開發。Here, we rename the first, second, and third columns to Backlog, Analyze, and Develop. 接著,我們會新增資料行並標示其測試。We then add a column and label it Test.

    您可以直接從儀表板面板重新命名資料行。You can rename a column directly from the Kanban board.

    Kanban board, rename a column directly

    或者,您可以開啟對話方塊,並變更一個或多個「查看板」資料行的設定。Or, you can open the dialog and change one or more settings for a Kanban column.

    Kanban board, Settings, Columns, Add and rename  columns, Agile process
  5. 若要變更資料行順序,請將 [資料行] 索引標籤拖曳至您想要的位置。To change the column order, drag the column tab to the position you want.

  6. 若要刪除資料行,請先確認資料行未包含任何工作專案。To delete a column, first make sure that the column doesn't contain any work items. 如果有的話,請將專案移到另一個資料行。If it does, move the items to another column. 然後,選擇 [資料行] 索引標籤 動作圖示,然後從功能表中選取 [ 刪除 ]。

    將資料行刪除的儀表板面板

  1. 開啟您的看板面板Open your Kanban board. 如果您不是小組系統管理員,請 加入成為一個系統管理員。If you're not a team admin, get added as one. 只有 team 和 project admins 可以自訂該儀表板。Only team and project admins can customize the Kanban board.

  2. 齒輪圖示,用以開啟儀表板面板的 [一般設定] 設定對話方塊。

    [儀表板],開啟一般設定

    TFS 2015。1TFS 2015.1

  3. 選擇 [資料 ],然後選擇 [資料行] 索引標籤,以查看您可以修改的所有設定。Choose Columns and then a column tab to see all the settings you can modify. 您的初始資料行設定看起來會像這樣。Your initial column settings will look something like this.

    自訂資料行、自訂資料行、預設資料行、適用于 TFS 2015.1 的 Agile 程式

  4. 變更您的資料行標題,以對應至您的工作流程階段。Change your column titles to map to your workflow stages. 您可以新增、重新命名和移動資料行,以支援更多階段。You can add, rename, and move columns to support more stages.

    在這裡,我們會將第一個、第二個和第三個數據行重新命名為待處理專案、分析和開發。Here, we rename the first, second, and third columns to Backlog, Analyze, and Develop. 接著,我們會新增資料行並標示其測試。We then add a column and label it Test.

    您可以直接從儀表板面板重新命名資料行。You can rename a column directly from the Kanban board.

    儀表板面板,直接重新命名資料行

    或者,您可以開啟對話方塊,並變更一個或多個「查看板」資料行的設定。Or, you can open the dialog and change one or more settings for a Kanban column.

    儀表板、新增和重新命名資料行

  5. 若要變更資料行順序,請將 [資料行] 索引標籤拖曳至您想要的位置。To change the column order, drag the column tab to the position you want.

  6. 若要刪除資料行,請先確認資料行未包含任何工作專案。To delete a column, first make sure that the column doesn't contain any work items. 如果有的話,請將專案移到另一個資料行。If it does, move the items to another column. 然後,選擇 [資料行] 索引標籤 動作圖示,然後從功能表中選取 [ 刪除 ]。

    將資料行刪除的儀表板面板

  7. 視需要變更 新增的資料行、新增的工作流程狀態,或新增工作專案類型 (wit) 所需的狀態對應。Change State mappings as needed for added columns, added workflow states, or added work item types (WITs).

    當您變更 [使用 bug ] 設定或 [將 Wit 新增至需求] 分類時,通常需要執行更新 狀態 對應。Usually you need to do update State mappings when you change the Working with bugs setting or add WITs to the Requirement Category.

  8. 完成變更之後,請選擇 [ 儲存]。When done with your changes, choose Save.

    TFS 2015TFS 2015

  9. 變更您的資料行標題,以對應至您的工作流程階段。Change your column titles to map to your workflow stages. 您可以新增、重新命名和移動資料行,以支援更多階段。You can add, rename, and move columns to support more stages.

    看板、自訂資料行、預設資料行、Agile 流程

    在這裡,我們會將第一個、第二個和第三個數據行重新命名為待處理專案、分析和開發。Here, we rename the first, second, and third columns to Backlog, Analyze, and Develop. 接著,我們會新增資料行並標示其測試。We then add a column and label it Test.

    自訂資料行、加入資料行

    重新命名資料行標題,以最符合工作的每個階段。Rename column titles to best reflect each stage of work. 盡可能將資料行標題保持簡單。Keep the column titles as simple as possible.

  10. 若要變更資料行順序,請使用左←或右→箭號圖示。To change the column order, use the left ← or right → arrow icons.

  11. 若要刪除資料行,請先確認資料行未包含任何工作專案。To delete a column, first make sure that the column doesn't contain any work items. 如果有的話,請將專案移到另一個資料行。If it does, move the items to another column. 然後按一下資料行頂端的 [X]。Then, click X at the top of the column.

  12. 視需要變更 新增的資料行、新增的工作流程狀態,或新增工作專案類型 (wit) 所需的狀態對應。Change State mappings as needed for added columns, added workflow states, or added work item types (WITs).

    當您變更 [使用 bug ] 設定或 [將 Wit 新增至需求] 分類時,通常需要更新 狀態 對應。Usually you need to update State mappings when you change the Working with bugs setting or add WITs to the Requirement Category.

  1. 開啟您的看板面板Open your Kanban board. 如果您不是小組系統管理員,請 加入成為一個系統管理員。If you're not a team admin, get added as one. 只有 team 和 project admins 可以自訂該儀表板。Only team and project admins can customize the Kanban board.

  2. 選擇 齒輪圖示以開啟 [自訂資料行]。

    [儀表板],開啟一般設定

    如果您不是小組系統管理員,請 加入成為一個系統管理員。If you're not a team admin, get added as one. 只有 team 和 project admins 可以自訂資料行。Only team and project admins can customize columns.

    看板、自訂資料行、預設資料行、Agile 流程

  3. 變更您的資料行標題,以對應至您的工作流程階段。Change your column titles to map to your workflow stages. 您可以新增、重新命名和移動資料行,以支援更多階段。You can add, rename, and move columns to support more stages.

    在這裡,我們會將第一個、第二個和第三個數據行重新命名為待處理專案、分析和開發。Here, we rename the first, second, and third columns to Backlog, Analyze, and Develop. 接著,我們會新增資料行並標示其測試。We then add a column and label it Test.

    自訂資料行、加入資料行

    重新命名資料行標題,以最符合工作的每個階段。Rename column titles to best reflect each stage of work. 盡可能將資料行標題保持簡單。Keep the column titles as simple as possible.

  4. 若要變更資料行順序,請使用左←或右→箭號圖示。To change the column order, use the left ← or right → arrow icons.

  5. 若要刪除資料行,請先確認資料行未包含任何工作專案。To delete a column, first make sure that the column doesn't contain any work items. 如果有的話,請將專案移到另一個資料行。If it does, move the items to another column. 然後,選擇資料行頂端的 [ X ]。Then, choose X at the top of the column.

  6. 視需要變更 新增的資料行、新增的工作流程狀態,或新增工作專案類型 (wit) 所需的狀態對應。Change State mappings as needed for added columns, added workflow states, or added work item types (WITs).

    當您變更 [使用 bug ] 設定或 [將 Wit 新增至需求] 分類時,通常需要更新 狀態 對應。Usually you need to update State mappings when you change the Working with bugs setting or add WITs to the Requirement Category.

使用您的看板面板Use your Kanban board

設定好的儀表板面板之後,您就可以開始使用它。Once you have a well-configured Kanban board, you can start using it. 若要深入瞭解,請參閱 開始使用您的看板面板To learn how, see Start using your Kanban board.

重要

出現在多個小組的看板上的工作專案,可能會產生不符合您預期的結果。Work items that appear on more than one team's Kanban board can yield results that don't meet your expectations. 每個小組都可以自訂儀表板面板資料行和泳道。Each team can customize the Kanban board columns and swimlanes. 因此,當另一個小組從不同的面板更新工作專案時,指派給 面板資料行面板泳道 的值可能會與您預期的不同。Therefore, the values assigned to Board Column or Board Swimlane may differ from what you expect when another team updates the work item from a different board.

解決此問題的主要工作是藉由 定義區域路徑並指派給小組,來維護工作專案的單一擁有權。The primary work around for this issue is to maintain single ownership of work items by Defining area paths and assign to a team. 另一個選項是新增所有小組都可以使用的自訂工作流程狀態。Another option is to add custom workflow states which all teams can use. 如需詳細資訊,請參閱 自訂工作流程 (繼承流程) For details, see Customize the workflow (Inheritance process).

重要

出現在多個小組的看板上的工作專案,可能會產生不符合您預期的結果。Work items that appear on more than one team's Kanban board can yield results that don't meet your expectations. 每個小組都可以自訂儀表板面板資料行和泳道。Each team can customize the Kanban board columns and swimlanes. 因此,當另一個小組從不同的面板更新工作專案時,指派給 面板資料行面板泳道 的值可能會與您預期的不同。Therefore, the values assigned to Board Column or Board Swimlane may differ from what you expect when another team updates the work item from a different board.

解決此問題的主要工作是藉由 定義區域路徑並指派給小組,來維護工作專案的單一擁有權。The primary work around for this issue is to maintain single ownership of work items by Defining area paths and assign to a team. 另一個選項是新增所有小組都可以使用的自訂工作流程狀態。Another option is to add custom workflow states which all teams can use. 如需詳細資訊,請參閱 變更工作專案類型的工作流程For details, see Change the workflow for a work item type.

更新狀態和交付專案Update status and handoff items

使用您的看板面板無法簡化。Using your Kanban board couldn't be simpler. 您可以使用拖放作業來更新狀態或變更優先順序。Using drag-and-drop operations you update the status or change priorities.

例如,若要在下游階段中啟動工作時發出通知,請將專案拖曳至下一個資料行。For example, to signal when work can start in a downstream stage, drag items into the next column.

看板,移動項目

您會發現,您可以將專案從一個資料行移到面板上的任何其他資料行。You'll notice that you can move an item from one column to any other column on the board. 如此一來,如果您在先前的階段中發現需要更多工作,您可以將專案向後移動,例如從測試進入 [分析] 或 [開發]。That way, if you discover more work is needed at an earlier stage, you can move the item backward, for example from Test into Analyze or Develop.

此外,若要將工作移交給另一個小組成員,請直接從面板重新指派。Also, to handoff work to another team member, reassign it directly from the board.

工作流程看板,指派項目

而且,接收遞交的團隊成員可以 設定警示 ,以接收其新指派工作的立即電子郵件通知。And, team members receiving the handoff can set alerts to receive immediate email notifications of their newly assigned work.

變更優先順序Change priorities

為了讓小組能夠處理最高優先順序的專案,您會想要在工作開始時,于優先變更發生時快速回應。To keep teams working on the highest priority items, you'll want to react quickly when a change in priority occurs even after work starts. 在您的儀表板板上,它是一個嵌入式管理單元。With your Kanban board it's a snap. 只要在資料行中向上或向下拖曳專案即可。Simply drag an item up or down within a column.

看板資料行,在資料行內重新排列Kanban column, reorder within column

追蹤看板資料行狀態Track Kanban column status

您的儀表板面板是您用來追蹤工作的數個工具之一。Your Kanban board is one of several tools you have for tracking work. 查詢工具可讓您列出工作專案的子集,以供審查、分級、更新或圖表產生之用。The query tool allows you to list a subset of work items for the purposes of review, triage, update, or chart generation. 例如,您可以建立查詢來列出所有使用中的使用者案例 (指定兩個子句:工作專案類型 = 使用者案例;State = Active) 。For example, you can create a query to list all active user stories (specify two clauses: Work Item Type=User Story; State=Active).

但是,如果您想要根據工作表的資料行指派來列出專案,該怎麼辦?But what if you want to list items based on their Kanban column assignment? 可以這麼做嗎?Can you do that? 是的,您可以使用 [面板資料行] 和 [面板資料行完成] 欄位來追蹤看板面板資料行移動。Yes, you can track Kanban board column moves using the Board Column and Board Column Done fields.

但是,如果您想要根據工作表的資料行指派來列出專案,該怎麼辦?But what if you want to list items based on their Kanban column assignment? 可以這麼做嗎?Can you do that? 是,從 TFS 2015 Update 1 或更新版本。Yes, from TFS 2015 Update 1 or later version. 否,如果您是從 TFS 2015 或更早版本工作。No, if you work from TFS 2015 or earlier versions. 您可以使用 [面板資料行] 和 [面板資料行完成] 欄位來追蹤儀表板面板資料行移動。You track Kanban board column moves using the Board Column and Board Column Done fields.

Tfs 2013 的 tfs 2015: 您可以做的是查看對工作專案所做變更的歷程記錄。For TFS 2013, TFS 2015: What you can do is view the history of changes made to a work item. 歷程 [記錄] 欄位 會捕捉對專案所做的所有更新,包括資料行移動。The History field captures all updates made to an item, including column moves. 您可以藉由開啟卡片 (按兩下來開啟) 來查看歷程記錄。You can view history by opening the card (double-click to open).

例如,下列歷程記錄會顯示將專案拖曳到不同的 [檢視器] 資料行中所做的兩項更新。For example, the following History shows two updates made by dragging the item into a different Kanban column. 第一個 (修訂版 8) 牽涉到資料行移動,從分析到開發;而且狀態變更為「作用中」的新狀態。The first (revision 8) involved a column move, from Analyze to Develop; and a State change, New to Active. 不過,第二個 (修訂版 9) 只牽涉到資料行移動,從開發到測試;狀態會保持作用中。However, the second (revision 9) only involved a column move, from Develop to Test; the State remains at Active.

記錄欄位因看板資料行移動而更新History field updates with Kanban column moves

當專案的卡片從某個方程式資料行移到下一個時,專案的工作流程狀態會根據該資料列對狀態的對應進行更新。As an item's card moves from one Kanban column to the next, the item's workflow state updates based on the Kanban column-to-State mapping. 您可以從 [自訂資料行] 對話方塊查看並設定這些對應。You can see and set these mappings from the Customize Columns dialog. 例如,以下是 Agile 使用者案例的預設對應。For example, here's the default mapping for the Agile user story.

看板狀態對應的資料行Kanban column to State mappings

看板資料行可能會對應到實際的工作流程狀態或虛擬狀態。Kanban columns may correspond to an actual workflow state or a pseudo state. 例如,[開發]、[測試] 和 [確認] 資料行可能會全部對應到 [使用中] 狀態。For example, Develop, Test, and Verify columns may all map to the Active state. 在此情況下,當您將專案從 [開發] 移至 [測試] 或 [測試] 以進行驗證時,專案的狀態不會變更。In this case, when you move an item from Develop to Test or from Test to Verify, the item's State doesn't change.

常見問題集FAQs

支援的 Marketplace 延伸模組Supported Marketplace extensions

這就是您在處理看看看看看看資料行的所有須知。That's about all you need to know about working with Kanban columns. 以下是一些您可以用來自訂面板外觀和風格的選項。Here are a few more options you have for customizing the look and feel of the board.

REST API 資源REST API resources

若要以程式設計方式與儀表板和其他小組設定互動,請參閱 REST API 的面板 參考To interact programmatically with Kanban board and other team settings, see the REST API, Boards reference.