Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Azure DevOps Services | Azure DevOps Server | Azure DevOps Server 2022
Work items are the backbone for planning and tracking work. As such, make sure each work item type (WIT) tracks the data your team needs.
Important
The Inheritance process model is available for projects that are configured to support the model type. If you use an older collection, check the process model compatibility. If your on-premises collection is configured to use the on-premises XML process model, you can only use that process model to customize the work tracking experience. For more information, see Organization-level process customization.
To support your work tracking requirements, customize each WIT to add custom groups for collecting custom fields under a common section. Organize your forms by placing logically related groups and HTML fields on separate pages within a form to minimize clutter on any one page within the form.
For example, the following form shows that you added two custom pages, Impact and Mitigation. In addition, you added several new groups and fields to the Details page.
After you add a custom page or group, you can add custom fields to those pages or groups. To learn more about what you can customize, see About process customization and inherited processes.
Prerequisites
For guidance on tailoring Azure Boards to align with your specific business requirements, see Configure and customize Azure Boards.
| Category | Requirements |
|---|---|
| Permissions | - To create, delete, or edit a process: Member of the Project Collection Administrators 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. - To update boards: Team Administrator or a member of the Project Administrators group. |
| Access | - Even if you have Basic or lower access, you can still change a process if someone gives you permission. - To update and change the type of your existing work items: Member of the project. |
| Project process model | - Have the Inheritance process model for the project collection containing the project. - To migrate data to Azure DevOps Services, use the Team Foundation Server Database Import Service. |
| Knowledge | - Familiarity with the customization and process models. |
Open organization process settings
Sign in to your organization (
https://dev.azure.com/{yourorganization}).Select
Organization settings.
Select Process.
Sign in to your collection (
https://dev.azure.com/{Your_Collection}).Select Collection Settings or Admin settings.
Select Process.
Note
When you customize an inherited process, any projects that use the process automatically reflect the customizations. To ensure a smooth transition, we recommend that you create a test process and project to test your customizations before you implement them organization-wide. For more information, see Create and manage inherited processes.
Add a custom group
You can add your own custom groups to both inherited pages and custom pages.
From the Layout page, select New group.
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.
Enter a name for the group and choose the column where it should appear. For information about columns, see About process customization and inherited processes, Layout and resizing.
(Optional) After you add the group, you can drag and drop the group into any column or within the column. You can also select the Move Up or Move Down options from the group's … context menu.
Delete or remove a custom group
Before you remove a group, move all fields defined in that group to another group or remove them from the form.
Tip
You must remove all fields from a group for the Remove option to appear.
Select the 
Remove option from the custom group … context menu.
Note
When you hide all fields in an inherited group, the inherited group itself doesn't appear on the form.
Move a field
Within a page, you can quickly drag and drop a field to a new group or section within the page.
To move a field to another page, choose Edit from the field's … context menu and then choose the Page from the menu. Optionally, select an existing group or create a new group.
In the following example, you move the Customer ticket field to the Details page and the Customer focus group.
Remove a field from a form
You can only remove custom fields from a form. For inherited fields, you can hide them from showing on the form. For more information, see Customize a field for a process, Show, hide, or remove a field.
Add a custom page
Add a custom page when you have several custom fields that you want to group within that page. You can add and reorder custom pages.
From the Layout page of your selected WIT, select New page.
Label the page.
When you finish adding groups and fields to the page, verify your layout is as expected. Refresh your browser and open a work item of the type you just customized.
Reorder pages
You can reorder custom pages by using drag and drop, or by choosing the move operation from the custom page … context menu. You can't move the inherited Details page.
Delete a page
Before you delete a page, move any fields that your team still uses to another page.
Choose the Delete option from the custom page … context menu.
Note
Deleting a page doesn't delete any data. Once you define data for a field, the data stays in the data store and work item history, even if you remove the field from the form. You can always add the field back by choosing New field and selecting Use an existing field.
Related content
Note
You can review changes made to an inherited process by using the audit log and auditing features. For more information, see Access, export, and filter audit logs.