add-custom-field.md

title	titleSuffix	description	ms.custom	ms.service	ms.assetid	ms.author	author	ms.topic	monikerRange	ms.date
Add a custom field to an inherited process	Azure DevOps Services	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.	inherited-process	azure-devops-boards	D6616411-43D4-4A81-8951-772D98BD1569	chcomley	chcomley	quickstart	<= azure-devops	08/03/2022

Add a custom field to a work item type (Inheritance process)

[!INCLUDE version-lt-eq-azure-devops]

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. For a description of each field defined with a system process, see Work item field index.

[!INCLUDE temp]

For more information, see About process customization and inherited processes.

Tip

To customize a single project, always start by creating an inherited process and updating your project to that process. Then, all the customizations that you make to the inherited process automatically appear for the project you migrated.

Prerequisites

[!INCLUDE temp]

[!INCLUDE temp]

Create inherited process

For more information, see Create inherited process.

Add a field

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.

1. From the Process page of the selected inherited process, choose the work item type you want to add the custom field to.

   Here we choose the Bug WIT. The breadcrumb links allow you to move back to the All Processes and MyAgile process page.

   [!div class="mx-imgBorder"]
   

   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.

2. With the WIT selected, choose the :::image type="icon" source="media/process/new-field-icon.png" border="false"::: New field.

   [!div class="mx-imgBorder"]
   

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?. Optionally, add a Description.

   [!NOTE]
   Once created, you can't change the field name or data type.

   Here we add an Integer field labeled Customer Ticket.

   

   Additional data types you can add include: Picklist, Identity, Rich-text, HTML, and Checkbox.

4. (Optional) On the Options tab, indicate if the field is required and specify a default value. Or leave these blank.

   

   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.

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.

   Here, we add the Customer Ticket field to a new group labeled Customer focus.

   

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.

   [!TIP]
   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 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.

Verify the customization you made

We recommend that you create a test project and apply your customized inherited process to it to verify the changes you've made.

1. Open the All processes page, and choose the … context menu for the process you want to use, and then select New team project.

   ::: moniker range="azure-devops"

   [!div class="mx-imgBorder"]
   ::: moniker-end ::: moniker range=">= azure-devops-2020 < azure-devops" [!div class="mx-imgBorder"]
   ::: moniker-end

2. The Create new project page opens. Fill out the form.

   ::: moniker range="azure-devops"

   [!div class="mx-imgBorder"]
   ::: moniker-end ::: moniker range=">= azure-devops-2020 < azure-devops" [!div class="mx-imgBorder"]
   ::: moniker-end

3. Open Work Items. (1) Check that you have selected the right project, then (2) choose Work>Work Items.

   [!div class="mx-imgBorder"]
   

4. Select the WIT you customized. Here we choose Bug.

   [!div class="mx-imgBorder"]
   

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.

   [!div class="mx-imgBorder"]
   

[!INCLUDE temp]

Next steps

[!div class="nextstepaction"] Add a custom work item type Or Add or manage fields

Related articles

[!INCLUDE temp]

• View work item fields and attributes
• Add and manage fields for an inherited process
• Customize a project using an inherited process
• Create and manage inherited processes