You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/organizations/settings/includes/change-project-to-inherited-process.md
+9-12Lines changed: 9 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,31 +10,28 @@ ms.date: 07/20/2020
10
10
11
11
## Apply the customized process to your project
12
12
13
-
After you've verified your customizations, you can now apply the process to your existing project.
13
+
After you verify your customizations, you can now apply the process to your existing project.
14
14
15
15
> [!TIP]
16
-
> As you customize a WIT, all projects that reference the inherited process that you're customizing automatically updates to reflect the custom WITs you've added. To view your customizations, refresh your web browser.
16
+
> As you customize a WIT, all projects that reference the inherited process automatically update to reflect the custom WITs you added. To view your customizations, refresh your web browser.
17
17
18
18
::: moniker range=">= azure-devops-2020"
19
19
20
-
1. For the process currently used by the project, choose the number of projects.
20
+
1. For the process currently used by the project, choose the number of the project.
21
21
22
-
Here we open the menu for the Agile default process.
22
+
This is the Agile default process.
23
23
24
-
> [!div class="mx-imgBorder"]
25
-
> 
24
+
:::image type="content" source="/azure/devops/organizations/settings/work/media/process/choose-process-team-projects.png" alt-text="Screenshot shows the number for the team project, as a link.":::
26
25
27
26
1. Open the … context menu for the project you want to change, and choose the **Change process** option.
:::image type="content" source="/azure/devops/organizations/settings/work/media/process/choose-change-process.png" alt-text="Screenshot shows the project created with the Change process option.":::
33
31
34
-
1. From the Change the project process dialog, choose the process from the menu of options. And, then choose **Save**.
32
+
1. From the **Change the project process** dialog, choose the process from the menu of options. And, then choose **Save**.
35
33
36
-
> [!div class="mx-imgBorder"]
37
-
> 
34
+
:::image type="content" source="/azure/devops/organizations/settings/work/media/process/change-project-process-inherited-agile.png" alt-text="Screenshot shows the Change the project process dialog with Agile Inherited selected.":::
Copy file name to clipboardExpand all lines: docs/organizations/settings/includes/process-prerequisites.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,11 +2,11 @@
2
2
ms.topic: include
3
3
---
4
4
5
-
For guidance on tailoring Azure Boards to align with your specific business requirements, see [About configuring and customizing Azure Boards](../../../boards/configure-customize.md).
5
+
For guidance on tailoring Azure Boards to align with your specific business requirements, see [Configure and customize Azure Boards](../../../boards/configure-customize.md).
6
6
7
7
| Category | Requirements |
8
8
|--------------|-------------|
9
-
|**Permissions**| - To create, delete, or edit a process: Member of the [Project Collection Administrators](../../security/change-organization-collection-level-permissions.md) group or specific collection-level permissions **Create process**, **Delete process**, **Edit process**, or **Delete a field from organization** set to **Allow**. For more information, see [Set permissions and access for work tracking, Customize an inherited process](../../../security/set-permissions-access-work-tracking.md#customize-an-inherited-process).<br>- To update boards: [Team Administrator](../add-team-administrator.md) or a member of the [Project Administrators](../../security/change-project-level-permissions.md) group. |
9
+
|**Permissions**| - To create, delete, or edit a process: Member of the [Project Collection Administrators](../../security/change-organization-collection-level-permissions.md) group or specific collection-level permissions **Create process**, **Delete process**, **Edit process**, or **Delete a field from organization** set to **Allow**. For more information, see [Customize an inherited process](../../../security/set-permissions-access-work-tracking.md#customize-an-inherited-process).<br>- To update boards: [Team Administrator](../add-team-administrator.md) or a member of the [Project Administrators](../../security/change-project-level-permissions.md) group. |
10
10
|**Access**| - Even if you have **Basic** or lower access, you can still change a process if someone gives you permissions to do so.<br>- To update and change the type of your existing work items: Member of the project. |
11
11
|**Project process model**| - Have the [Inheritance process model](../../../reference/customize-work.md#choose-the-process-model-for-your-project-collection) for the project collection containing the project.<br>- If migrating data to Azure DevOps Services, use the [Team Foundation Server Database Import Service](../../../migrate/migration-overview.md). |
12
12
|**Knowledge**| Familiarity with the [customization and process models](../../../reference/customize-work.md). |
Copy file name to clipboardExpand all lines: docs/organizations/settings/work/add-custom-field.md
+38-49Lines changed: 38 additions & 49 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,22 +1,23 @@
1
1
---
2
-
title: Add a custom field to an inherited process
2
+
title: Add a Custom Field to an Inherited Process
3
3
titleSuffix: Azure DevOps Services
4
-
description: Learn how to add a custom field to the web form of a work item type for an Inheritance process model and apply it to a project.
4
+
description: In this quickstart, learn how to add a custom field to the web form of a work item type for an Inheritance process model and apply it to a project.
5
5
ms.custom: inherited-process
6
6
ms.service: azure-devops-boards
7
7
ms.assetid: D6616411-43D4-4A81-8951-772D98BD1569
8
8
ms.author: chcomley
9
9
author: chcomley
10
10
ms.topic: quickstart
11
11
monikerRange: '<= azure-devops'
12
-
ms.date: 08/03/2022
12
+
ms.date: 07/31/2025
13
+
#customer intent: As a team leader, I want to know how to add a custom field to my work items in Azure Boards.
13
14
---
14
15
15
-
# Add a custom field to a work item type (Inheritance process)
16
+
# Quickstart: Add a custom field to a work item type (Inheritance process)
You add a custom field to support tracking data requirements you have that aren't met with the existing set of fields. For example, you can add a custom field to track a customer ticket number. For a list of all fields defined for your organization—which includes all fields defined for system and inherited processes—see [View work item fields and attributes](../../../boards/work-items/work-item-fields.md). For a description of each field defined with a system process, see [Work item field index](../../../boards/work-items/guidance/work-item-field.md).
20
+
In this quickstart, you add a custom field to support tracking data requirements you have that aren't met with the existing set of fields. For example, you can add a custom field to track a customer ticket number. For a list of all fields defined for your organization, which includes all fields defined for system and inherited processes, see [List work item fields and attributes](../../../boards/work-items/work-item-fields.md). For a description of each field defined with a system process, see [Default and work item fields used in process templates](../../../boards/work-items/guidance/work-item-field.md).
@@ -33,103 +34,91 @@ For more information, see [About process customization and inherited processes](
33
34
34
35
## Create inherited process
35
36
36
-
For more information, see [Create inherited process](manage-process.md#create-an-inherited-process).
37
+
For more information, see [Create an inherited process](manage-process.md#create-an-inherited-process).
37
38
38
39
<aid="add-wit"> </a>
39
40
40
41
## Add a field
41
42
42
43
Do the following steps to add a field to an existing work item type. You can't use the **Steps** control on a custom work item type based on the Test Case work item type.
43
44
44
-
1. From the **Process** page of the selected inherited process, choose the work item type you want to add the custom field to.
45
+
1. From the **Process** page of the selected inherited process, choose the work item type (WIT) you want to add the custom field to.
45
46
46
-
Here we choose the Bug WIT. The breadcrumb links allow you to move back to the **All Processes** and **MyAgile** process page.
47
+
This example uses the Bug WIT. The breadcrumb links allow you to move back to the **All Processes** and **MyAgile** process page.
:::image type="content" source="media/field/breadcrumbs-bug-wit.png" alt-text="Screenshot shows the process page for MyAgile, showing a bug.":::
50
50
51
-
If the **New field** and other options are disabled, you don't have the necessary permissions to edit the process. See [Set permissions and access for work tracking, Customize an inherited process](../../../organizations/security/set-permissions-access-work-tracking.md#customize-an-inherited-process).
51
+
If the **New field** and other options are disabled, you don't have the necessary permissions to edit the process. See [Customize an inherited process](../../../organizations/security/set-permissions-access-work-tracking.md#customize-an-inherited-process).
52
52
53
-
2. With the WIT selected, choose the :::image type="icon" source="media/process/new-field-icon.png" border="false"::: **New field**.
53
+
1. With the WIT selected, choose the :::image type="icon" source="media/process/new-field-icon.png"::: **New field**.
54
54
55
-
> [!div class="mx-imgBorder"]
56
-
> 
55
+
:::image type="content" source="media/field/bug-new-field.png" alt-text="Screenshot shows the process page for a WIT with New field highlighted.":::
57
56
58
-
3. Name the field and select the field type from one of the supported data types. Field names must be unique and no more than 128 characters. For additional restrictions, see [What is a field? How are field names used?](inheritance-process-model.md#field-reference). Optionally, add a Description.
57
+
1. Name the field and select the field type from one of the supported data types. Field names must be unique and no more than 128 characters. For other restrictions, see [What is a field? How are field names used?](inheritance-process-model.md#field-reference) Optionally, add a description.
59
58
60
59
> [!NOTE]
61
60
> Once created, you can't change the field name or data type.
62
61
63
-
Here we add an Integer field labeled Customer Ticket.
62
+
This example adds an Integer field labeled Customer Ticket.
64
63
65
-
<img src="media/process/cpfield-add-field-to-bug-type-integer-up1.png" alt="Add a field to Bug, choose field type" />
64
+
:::image type="content" source="media/process/cpfield-add-field-to-bug-type-integer-up1.png" alt-text="Screenshot shows the Create a field option for a Bug.":::
66
65
67
-
Additional data types you can add include: [Picklist](customize-process-field.md#add-a-picklist), [Identity](customize-process-field.md#add-an-identity-field), [Rich-text, HTML](customize-process-field.md#add-a-rich-text-html-field), and [Checkbox](customize-process-field.md#add-a-checkbox-field).
66
+
Other data types you can add include: [Picklist](customize-process-field.md#add-a-picklist), [Identity](customize-process-field.md#add-an-identity-field), [Rich-text, HTML](customize-process-field.md#add-a-rich-text-html-field), and [Checkbox](customize-process-field.md#add-a-checkbox-field).
68
67
69
68
<a id="options"> </a>
70
-
4. (Optional) On the **Options** tab, indicate if the field is required and specify a default value. Or leave these blank.
69
+
1.(Optional) On the **Options** tab, indicate if the field is required. Specify a default value.
71
70
72
-
<img src="media/process/cpfield-bug-customer-ticket-options.png" alt="Add a field to Use story, specify options" />
71
+
:::image type="content" source="media/process/cpfield-bug-customer-ticket-options.png" alt-text="Screenshot shows the Options page where you can make the field required and specify a default value.":::
73
72
74
-
By making a field Required, users must specify a value for the field in order to save it. The default value you specify is set when you create a work item as well as every time a work item is opened and the field is empty.
73
+
If a field is required, users must specify a value for the field in order to save it. The default value you specify is set when you create a work item and every time a work item is opened and the field is empty.
75
74
76
75
<a id="layout"> </a>
77
-
5. (Optional) On the **Layout** tab, you can enter a different form label than the name of the field. Also, you can choose the page and group where the field appears on the form.
76
+
1.(Optional) On the **Layout** tab, you can enter a different form label than the name of the field. Also, you can choose the page and group where the field appears on the form.
78
77
79
-
Here, we add the Customer Ticket field to a new group labeled Customer focus.
78
+
This example adds the Customer Ticket field to a new group labeled Customer focus.
80
79
81
-
<img src="media/process/cpfield-customer-ticket-layout.png" alt="Add a field to Use story, specify layout" />
80
+
:::image type="content" source="media/process/cpfield-customer-ticket-layout.png" alt-text="Screenshot shows the Layout page where you can specify how the field is displayed.":::
82
81
83
-
6. Choose **Add field** to complete adding the field. If you haven't specified its layout location, it is added to the first group of fields on the layout form.
82
+
1.Choose **Add field** to complete adding the field. If you don't specify its layout location, it's added to the first group of fields on the layout form.
84
83
85
84
> [!TIP]
86
-
> Once you've added a field, you can drag-and-drop it within a page to relocate it on the form. If you have several fields you want to add to a custom page or group, then you may want to [add those elements first](customize-process-form.md) and then add your fields. You can't add a field to the gray area within the form where the Assigned To, State, and Reason fields are located.
85
+
> After you add a field, you can drag-and-drop it within a page to relocate it on the form. If you have several fields you want to add to a custom page or group, [add those elements first](customize-process-form.md) and then add your fields. You can't add a field to the gray area within the form where the **Assigned To**, **State**, and **Reason** fields are located.
87
86
88
87
<aid="verify"> </a>
89
88
90
89
## Verify the customization you made
91
90
92
-
We recommend that you create a test project and apply your customized inherited process to it to verify the changes you've made.
91
+
We recommend that you create a test project and apply your customized inherited process to it to verify the changes you made.
93
92
94
-
1. Open the **All processes** page, and choose the … context menu for the process you want to use, and then select **New team project**.
93
+
1. Open the **All processes** page, and choose the … context menu for the process you want to use. Then select **New team project**.
95
94
96
95
::: moniker range="azure-devops"
97
-
> [!div class="mx-imgBorder"]
98
-
> 
96
+
:::image type="content" source="media/process/new-team-project-from-inherited-process-menu.png" alt-text="Screenshot shows the create a project option for a selected process.":::
> 
99
+
:::image type="content" source="media/add-custom-field/choose-new-team-project.png" alt-text="Screenshot shows the create a project option for your modified process.":::
103
100
::: moniker-end
104
-
105
101
106
-
2. The Create new project page opens. Fill out the form.
102
+
1. The **Create new project** page opens. Fill out the form.
107
103
108
104
::: moniker range="azure-devops"
109
-
> [!div class="mx-imgBorder"]
110
-
> 
105
+
:::image type="content" source="media/process/create-test-project-sprint166.png" alt-text="Screenshot shows the Create new project form.":::
:::image type="content" source="../../../boards/work-items/media/view-add/open-work-items-agile.png" alt-text="Screenshot shows Azure Boards with Work items selected.":::
122
114
123
-
4. Select the WIT you customized. Here we choose**Bug**.
115
+
1. Select the WIT you customized, in this example,**Bug**.
124
116
125
-
> [!div class="mx-imgBorder"]
126
-
> 
117
+
:::image type="content" source="media/process/add-custom-field-verify-bug.png" alt-text="Screenshot shows New Work Item with the Bug item selected.":::
127
118
128
-
5. Verify that the field you added appears on the form. Note that the :::image type="icon" source="../../../media/icons/required-icon.png" border="false"::: (exclamation mark) icon indicates the field is required.
119
+
1. Verify that the field you added appears on the form. The :::image type="icon" source="../../../media/icons/required-icon.png"::: (exclamation mark) icon indicates the field is required.
129
120
130
-
> [!div class="mx-imgBorder"]
131
-
> 
132
-
121
+
:::image type="content" source="media/process/add-custom-field-verify-bug-form.png" alt-text="Screenshot shows the New Bug with the Customer Ticket field added.":::
0 commit comments