Merge pull request #8180 from TimShererWithAquent/us449229-10

Freshness Edit: Azure DevOps - Boards & Organizations

Author: v-regandowner

docs/organizations/settings/includes/automatic-update-project.md

@@ -9,4 +9,4 @@ ms.date: 05/31/2024
 
 
 > [!NOTE]   
-> When you customize an inherited process, any projects using that process automatically reflect the customizations. To ensure a smooth transition, we recommend creating a test process and project, which allows you to test your customizations before you implement them organization-wide. For more information, see [Create and manage inherited processes](../work/manage-process.md).
+> 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](../work/manage-process.md).

docs/organizations/settings/work/custom-rules.md

@@ -1,39 +1,40 @@
 ---
-title: Add a custom rule to a work item type
+title: Add a Custom Rule to a Work Item Type
 titleSuffix: Azure DevOps Services
-description: Add a custom rule to a work item type defined for an inherited process and project
+description: Learn how to add a custom rule to a work item type defined for an inherited process and project in Azure Boards.
 ms.custom: inherited-process
 ms.service: azure-devops-boards
 ms.assetid: 17A6AF2C-81E9-4717-971E-2621613AEB31
 ms.author: chcomley
 author: chcomley
 monikerRange: "<=azure-devops"
 ms.topic: how-to
-ms.date: 06/07/2021
+ms.date: 08/04/2025
+#customer intent:  As a team leader, I want to know how to add rules to work items in Azure Boards.
 ---
 
 # Add a rule to a work item type (Inheritance process)
 
 [!INCLUDE [version-gt-eq-2019](../../../includes/version-gt-eq-2019.md)]
 
-Custom rules provide support for a number of business use cases, allowing you to go beyond setting a default value for a field or make it required. Rules allow you to clear the value of a field, copy a value into a field, and apply values based on dependencies between different fields' values. 
+Custom rules provide support for several business use cases. You can go beyond setting a default value for a field or make it required. Rules allow you to clear the value of a field, copy a value into a field, and apply values based on dependencies between different fields' values. 
 
 [!INCLUDE [temp](../includes/note-on-prem-link.md)]
 
-With a custom rule, you can define a number of actions based on specific conditions. For example, you can apply a rule to support these types of scenarios:
+With a custom rule, you can define actions based on specific conditions. For example, you can apply a rule to support these types of scenarios:
 
-- When a value is defined for Priority, then make Risk a required field
-- When a change is made to the value of Release, then clear the value of "Milestone"
-- When a change was made to the value of Remaining Work, then make Completed Work a required field
-- When the value of Approved is True, then make Approved By a required field
+- When a value is defined for Priority, make Risk a required field
+- When a change is made to the value of Release, clear the value of Milestone
+- When a change was made to the value of Remaining Work, make Completed Work a required field
+- When the value of Approved is True, make Approved By a required field
 - When a user story is created, make the following fields required: Priority, Risk, and Effort
-- When current user is a member of "Project Administrators", then make Priority required
-- When current user is not a member of "Project Administrators", then hide the Priority field
+- When current user is a member of Project Administrators, make Priority required
+- When current user isn't a member of Project Administrators, hide the Priority field
 
 > [!NOTE]  
-> You make a field required and specify a field default through the [**Options** tab for the field](customize-process-field.md#options).
+> You make a field required and specify a field default through the **Options** [tab for the field](customize-process-field.md#options).
 
-Prior to defining a custom rule, review [Rules and rule evaluation, Inherited process rule composition](rule-reference.md#ip-rule-composition). For examples that illustrate common scenarios for applying rules, see [Sample rule scenarios](rule-samples.md). 
+Before you define a custom rule, review [Inherited process rule composition](rule-reference.md#ip-rule-composition). For examples that illustrate common scenarios for applying rules, see [Sample custom rule scenarios](rule-samples.md). 
 
 ## Prerequisites
 
@@ -45,27 +46,26 @@ Prior to defining a custom rule, review [Rules and rule evaluation, Inherited pr
 
 ## Add a custom rule
 
-You add fields to a selected work item type.
+Add fields to a selected work item type.
 
-1.  Select the WIT to which you want to add a rule, choose **Rules**, and then choose **New rule**.
+1.  Select the work item type (WIT) to which you want to add a rule, choose **Rules**, and then choose **New rule**.
 
-    > [!div class="mx-imgBorder"]  
-    > ![Process, WIT, Bug, Layout, New rule](media/rules/custom-rule-create-rule.png)
+    :::image type="content" source="media/rules/custom-rule-create-rule.png" alt-text="Screenshot shows the My Agile Process user story with the Rules tab open ready to create a rule.":::
 
-    If you can't fill out the New work item rule dialog, 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).
+    If you can't fill out the New work item rule dialog, 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).
 
-1.  Name the rule and select the condition(s) and action(s) from the dropdown menus.
+1.  Name the rule and select the conditions and actions.
 
     > [!TIP]  
-    > Specify a name that builds off the field(s) you're acting on, or the conditions you're setting.
+    > Specify a name that builds off the fields you're acting on, or the conditions you're setting.
 
-    Here we define that the **Acceptance Criteria** field is required when the **State** changes to **Active** and it is currently empty.
+    This example specifies that the **Acceptance Criteria** field is required when the **State** changes to **Active** and it's currently empty.
 
-    <img src="media/process/custom-rule-create-rule-form.png" alt="New rule form" />
+    :::image type="content" source="media/process/custom-rule-create-rule-form.png" alt-text="Screenshot shows the New work rule form where you specify the rule content.":::
 
-	The sequence of actions you specify doesn't impact the behavior of the rule itself or its behavior with respect to other rules defined for the same WIT.
+	The sequence of actions you specify doesn't affect the behavior of the rule itself or its behavior with respect to other rules defined for the same WIT.
 
-1.  Once you've added a custom rule, open a work item and verify that the rule works as you intended.
+1.  After you add a custom rule, open a work item. Verify that the rule works as you intended.
 
 <a id="delete-disable"> </a>
 
@@ -75,7 +75,7 @@ You can temporarily disable a rule or delete it altogether.
 
 You delete or disable the rule from the actions menu of the rule.
 
-![Delete or disable a rule](media/process/custom-rule-delete-disable-rule.png)  
+:::image type="content" source="media/process/custom-rule-delete-disable-rule.png" alt-text="Screenshot shows the option to delete or disable a rule.":::  
 
 ## Related content