Skip to content
This repository was archived by the owner on Jan 21, 2026. It is now read-only.

Commit 7ba0cf9

Browse files
authored
Merge pull request #611 from MicrosoftLearning/azure-pass-retirement
Retire Azure Pass and fix bugs
2 parents d3b3ee2 + 7855ba8 commit 7ba0cf9

33 files changed

Lines changed: 829 additions & 1195 deletions

File tree

Allfiles/Demos/placeholder.txt

Whitespace-only changes.

Allfiles/Labs/placeholder.txt

Whitespace-only changes.

Instructions/Demos/00-setup.md

Lines changed: 0 additions & 78 deletions
This file was deleted.
Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
---
2+
demo:
3+
title: 'Customize team process'
4+
module: 'Module 01: Implement development for enterprise DevOps'
5+
---
6+
7+
# Customize team process
8+
9+
In this demo we'll create a custom Scrum-based process. The process will include a backlog item field designed to track to a proprietary eShopOnWeb ticket ID.
10+
11+
In Azure DevOps, you customize your work tracking experience through a process. A process defines the building blocks of the work item tracking system as well as other sub-systems you access through Azure DevOps. Whenever you create a team project, you select the process which contains the building blocks you want for your project. Azure DevOps supports two process types. The first, the core system processes (Scrum, Agile, and CMMI) are read-only, so you cannot customize them. The second type, inherited processes, you create based on core system processes, with the option of customizing their settings.
12+
13+
All processes are shared within the same organization. That is, one or more team projects can reference a single process. Instead of customizing a single team project, you customize a process. Changes made to the process automatically update all team projects that reference that process. Once you've created an inherited process, you can customize it, create team projects based on it, and migrate existing team projects to reference it. The Git team project can't be customized until it's migrated to an inherited process.
14+
15+
1. On the Azure DevOps page, click the **Azure DevOps** logo in the top left corner to navigate to the account root page.
16+
1. In the left bottom corner of the page, click **Organization settings**.
17+
1. In the **Organization Settings** vertical menu, in the **Boards** section, select **Process**.
18+
1. On the **All processes** pane, to the right of the **Scrum** entry, select the ellipsis symbol (...) and, in the dropdown menu, select **Create inherited process**.
19+
20+
![Screenshot of the create inherited process option.](../Labs/images/m1/EShop-WEB-inherited_v1.png)
21+
22+
1. In the **Create inherited process from Scrum** panel, in the **Process name (required)** textbox, type **Customized Scrum** and click **Create process**.
23+
1. Back on the **All processes** pane, click the **Customized Scrum** entry.
24+
25+
> **Note**: You may need to refresh the browser for the new process to become visible.
26+
27+
1. On the **All processes > Customized Scrum** pane, select **Product Backlog Item**.
28+
29+
![Screenshot of the Customized Scrum process template pane](../Labs/images/m1/EShop-WEB-pbi_field_name_v1.png)
30+
31+
1. On the **All processes > Customized Scrum > Product Backlog Item** pane, click **New field**.
32+
1. On the **Add a field to Product Backlog Item** panel, on the **Definition** tab, in the **Create a field** section, in the **Name** textbox, type **EShop Ticket ID**.
33+
34+
![Screenshot of the Create a field section.](../Labs/images/m1/EShop-WEB-pbi_v1.png)
35+
36+
1. On the **Add a field to Product Backlog Item** panel, click **Layout**.
37+
1. On the **Add a field to Product Backlog Item** panel, on the **Layout** tab, in the **Label** textbox, type **Ticket ID**, select the **Create a new group** option, in the **Group** textbox, type **eShopOnWeb**, and click **Add field**.
38+
39+
![Screenshot of the new group creation.](../Labs/images/m1/EShop-WEB-pbi_field_layout_v1.png)
40+
41+
> **Note**: Now that the customized process has been configured, let's switch to the eShopOnWeb project to use it.
42+
43+
1. Return to the **All processes** root using the breadcrumb path at the top of the **All processes > Customized Scrum > Product Backlog Item** pane.
44+
1. On the **All processes** pane, select the **Scrum** entry.
45+
46+
![Screenshot of the all processes pane.](../Labs/images/m1/scrum_v1.png)
47+
48+
> **Note**: Our current project uses **Scrum**.
49+
50+
1. On the **All processes > Scrum** pane, select the **Projects** tab.
51+
1. In the list of projects, in the row containing the **eShopOnWeb** entry, select the ellipsis symbol (...) and then select **Change process**.
52+
1. On the **Change the project process** pane, in the **Select a target process** dropdown list, select the **Customized Scrum** process, click **Save** and then click **Close**.
53+
54+
![Screenshot of the change the project process pane.](../Labs/images/m1/EShop-WEB-custom_scrum_v1.png)
55+
56+
1. Click the **Azure DevOps** logo in the top left corner to return to the account root page.
57+
1. On the **Projects** tab, select the entry representing the **eShopOnWeb** project.
58+
1. In the vertical menu on the left side of the **eShopOnWeb** page, select **Boards** and ensure that the **Work Items** pane is displayed.
59+
1. In the list of work items, click the first backlog item.
60+
1. Verify that you now have the **Ticket ID** field under the **eShopOnWeb** group, which was defined during the process customization. You can treat this like any other text field.
61+
62+
![Screenshot of the new custom field under the eShopOnWeb group.](../Labs/images/m1/EShop-WEB-verify_v1.png)
63+
64+
> **Note**: Once the work item is saved, Azure DevOps will also save the new custom information so that it will be available for queries and through the rest of Azure DevOps.

Instructions/Demos/placeholder.txt

Lines changed: 0 additions & 43 deletions
This file was deleted.

0 commit comments

Comments
 (0)