prereqs standardized

Author: chcomley

docs/boards/backlogs/add-link.md

@@ -24,33 +24,33 @@ Work item links are associations between two work items or a work item and anoth
 
 ::: moniker range=" azure-devops"
 
-| Prerequisite | Description |
+| Category | Requirements |
 |:-------------|:------------|
-| **Project Administrator or Contributor member** | [Project member](../../organizations/security/add-users-team-project.md) and member of the **Contributors** or **Project Administrators** security group. |
-| **Stakeholder access** | To add or modify work items, have at least [**Stakeholder** access](../../organizations/security/stakeholder-access.md). Users with **Stakeholder** access for public projects have full access to backlog and board features, like users with **Basic** access. For more information, see [Stakeholder access quick reference](../../organizations/security/stakeholder-access.md). |
-| **Contributor member or Allow permissions** | - To view or modify work items, have your **View work items in this node** and **Edit work items in this node** permissions set to **Allow**. By default, the **Contributors** group has this permission set to **Allow**. For more information, see [Set permissions and access for work tracking](../../organizations/security/set-permissions-access-work-tracking.md).</br>- To configure the integration options for a Classic release pipeline, have permissions to edit the release.</br>- To link work items to commits and pull requests, have your **Edit work items in this node** permissions set to **Allow** for the Area Path assigned to the work item. By default, the Contributors group has this permission set.</br>- To view work items, have your **View work items in this node** permissions set to **Allow** for the Area Path assigned to the work item. |
-| **Defined iterations** | To use the **Planning** pane, your team administrator must [define iteration (sprint) paths and configure team iterations](../../organizations/settings/set-iteration-paths-sprints.md). |
+| **Project access** | [Project member](../../organizations/security/add-users-team-project.md). |
+| **Permissions** | - Member of the **Contributors** or **Project Administrators** security group.<br> - To view or modify work items: **View work items in this node** and **Edit work items in this node** permissions set to **Allow**. By default, the **Contributors** group has this permission set to **Allow**. For more information, see [Set permissions and access for work tracking](../../organizations/security/set-permissions-access-work-tracking.md). <br> - To configure the integration options for a Classic release pipeline: **Edit** permissions for the release. <br> - To link work items to commits and pull requests: **Edit work items in this node** permissions set to **Allow** for the Area Path assigned to the work item. By default, the Contributors group has this permission. <br> - To view work items: **View work items in this node** permissions set to **Allow** for the Area Path assigned to the work item. |
+|**Access levels** | To add or modify work items: At least [**Stakeholder** access](../../organizations/security/stakeholder-access.md). Users with **Stakeholder** access for public projects have full access to backlog and board features, like users with **Basic** access. For more information, see [Stakeholder access quick reference](../../organizations/security/stakeholder-access.md).   |
+| **Defined iterations** | To use the **Planning** pane, your team administrator [defined iteration (sprint) paths and configured team iterations](../../organizations/settings/set-iteration-paths-sprints.md). |
 
 ::: moniker-end
 
 ::: moniker range=">= azure-devops-2020 < azure-devops"
 
-| Prerequisite | Description |
+| Category | Requirements |
 |:-------------|:------------|
-| **Project Administrator or Contributor member** | [Project member](../../organizations/security/add-users-team-project.md) and member of the **Contributors** or **Project Administrators** security group. |
-| **Stakeholder access** | To add or modify work items, have at least [**Stakeholder** access](../../organizations/security/stakeholder-access.md). |
-| **Contributor member or Allow permissions** | - To view or modify work items, have your **View work items in this node** and **Edit work items in this node** permissions set to **Allow**. By default, the **Contributors** group has this permission set to **Allow**. For more information, see [Set permissions and access for work tracking](../../organizations/security/set-permissions-access-work-tracking.md).<br>- To configure the integration options for a Classic release pipeline, have permissions to edit the release.<br>- To link work items to commits and pull requests, have your **Edit work items in this node** permissions set to **Allow** for the Area Path assigned to the work item. By default, the Contributors group has this permission set.<br>- To view work items, have your **View work items in this node** permissions set to **Allow** for the Area Path assigned to the work item. |
-| **Defined iterations** | To use the **Planning** pane, your team administrator must [define iteration (sprint) paths and configure team iterations](../../organizations/settings/set-iteration-paths-sprints.md). |
+| **Project access** | [Project member](../../organizations/security/add-users-team-project.md). |
+| **Permissions** | - Member of the **Contributors** or **Project Administrators** security group.<br> - To view or modify work items: **View work items in this node** and **Edit work items in this node** permissions set to **Allow**. By default, the **Contributors** group has this permission set to **Allow**. For more information, see [Set permissions and access for work tracking](../../organizations/security/set-permissions-access-work-tracking.md). <br> - To configure the integration options for a Classic release pipeline: **Edit** permissions for the release. <br> - To link work items to commits and pull requests: **Edit work items in this node** permissions set to **Allow** for the Area Path assigned to the work item. By default, the Contributors group has this permission. <br> - To view work items: **View work items in this node** permissions set to **Allow** for the Area Path assigned to the work item. |
+|**Access levels** | To add or modify work items: At least [**Stakeholder** access](../../organizations/security/stakeholder-access.md). Users with **Stakeholder** access for public projects have full access to backlog and board features, like users with **Basic** access. For more information, see [Stakeholder access quick reference](../../organizations/security/stakeholder-access.md).   |
+| **Defined iterations** | To use the **Planning** pane, your team administrator [defined iteration (sprint) paths and configured team iterations](../../organizations/settings/set-iteration-paths-sprints.md). |
 
 ::: moniker-end
 
 ::: moniker range="< azure-devops-2020"
 
-| Prerequisite | Description |
+| Category | Requirements |
 |:-------------|:------------|
-| **Project Administrator or Contributor member** | [Project member](../../organizations/security/add-users-team-project.md) and member of the **Contributors** or **Project Administrators** security group. |
-| **Stakeholder access** | To add or modify work items, have at least [**Stakeholder** access](../../organizations/security/stakeholder-access.md). |
-| **Contributor member or Allow permissions** | To view or modify work items, have your **View work items in this node** and **Edit work items in this node** permissions set to **Allow**. By default, the **Contributors** group has this permission set to **Allow**. For more information, see [Set permissions and access for work tracking](../../organizations/security/set-permissions-access-work-tracking.md). |
+| **Project access** | [Project member](../../organizations/security/add-users-team-project.md). |
+| **Permissions** | - Member of the **Contributors** or **Project Administrators** security group.<br> - To view or modify work items: **View work items in this node** and **Edit work items in this node** permissions set to **Allow**. By default, the **Contributors** group has this permission set to **Allow**. For more information, see [Set permissions and access for work tracking](../../organizations/security/set-permissions-access-work-tracking.md).|
+| **Access levels** | - To add or modify work items: At least [**Stakeholder** access](../../organizations/security/stakeholder-access.md). |
 | **Defined iterations** | To use the **Planning** pane, your team administrator must [define iteration (sprint) paths and configure team iterations](../../organizations/settings/set-iteration-paths-sprints.md). |
 
 ::: moniker-end

docs/boards/backlogs/automate-work-item-state-transitions.md

@@ -26,13 +26,17 @@ Rules are established at the team backlog level and are applicable to all work i
 
 ::: moniker range="azure-devops"
 
-**Permissions:** To configure work item automation rules for your team, be a [Team Administrator](../../organizations/settings/add-team-administrator.md)  or member of the [**Project Administrators**](../../organizations/security/change-project-level-permissions.md) group.
+| Category | Requirements |
+|:-------------|:------------|
+|**Permissions**| To configure work item automation rules for your team: [Team Administrator](../../organizations/settings/add-team-administrator.md) role or member of the [**Project Administrators**](../../organizations/security/change-project-level-permissions.md) group.|
 
 ::: moniker-end
 
 ::: moniker range="< azure-devops"
 
-**Permissions:** To configure team settings, be a [Team Administrator](../../organizations/settings/add-team-administrator.md) or member of the [**Project Administrators**](../../organizations/security/change-project-level-permissions.md) group.
+| Category | Requirements |
+|:-------------|:------------|
+|**Permissions**| To configure team settings: [Team Administrator](../../organizations/settings/add-team-administrator.md) role or member of the [**Project Administrators**](../../organizations/security/change-project-level-permissions.md) group.|
 
 ::: moniker-end
 

docs/boards/backlogs/configure-your-backlog-view.md

@@ -30,11 +30,12 @@ To maximize the effectiveness of your backlog management, it's crucial to config
 
 ## Prerequisites
 
-- **Project access**: Be a [project member](../../organizations/security/add-users-team-project.md)
-- **Permissions**: Be a member of the **Contributors** group.
-- **Access levels**: 
-  - To reorder a backlog or use the Forecast tool, have at least **Basic** access. Users with **Stakeholder** access can't reorder backlog items or use the Forecast tool. For more information, see [Stakeholder access quick reference](../../organizations/security/stakeholder-access.md).
-- **Configured backlogs**: Ensure that both product and portfolio backlogs are set up for your team.
+| Category | Requirements |
+|--------------|-------------|
+| **Project access** | [Project member](../../organizations/security/add-users-team-project.md). |
+| **Permissions** | Member of the **Contributors** group. |
+| **Access levels** | - To reorder a backlog or use the Forecast tool: At least **Basic** access. Users with **Stakeholder** access can't reorder backlog items or use the Forecast tool. For more information, see [Stakeholder access quick reference](../../organizations/security/stakeholder-access.md). |
+| **Configured backlogs** | Both product and portfolio backlogs set up for your team. |
 
 > [!TIP]
 > You can't sort your backlog directly by clicking on a column header. To view a sorted list, select **Create query** from your backlog. Save and open the query, then modify it to a flat list query if needed to apply sorting to the results. For more information about queries, see [Use the query editor to list and manage queries](../queries/using-queries.md).

docs/boards/backlogs/connect-work-items-to-git-dev-ops.md

@@ -48,20 +48,22 @@ From the **Development** control, you can quickly access branches, pull requests
 
 ::: moniker range="azure-devops"
 
-- **Project access**: Be a [project member](../../organizations/security/add-users-team-project.md)
-- **Permissions**: 
-  - Be a member of the **Contributors** or **Project Administrators** group. To get added, [Add users to a project or team](../../organizations/security/add-users-team-project.md) group.
-  - To view or modify work items, have your **View work items in this node** and **Edit work items in this node** permissions set to **Allow**. By default, the **Contributors** group has this permission set. For more information, see [Set permissions and access for work tracking](../../organizations/security/set-permissions-access-work-tracking.md).
-- **Access levels**: To reorder a backlog or use the Forecast tool, have at least **Basic** access. Users with **Stakeholder** access can't reorder backlog items or use the Forecast tool. For more information, see [Stakeholder access quick reference](../../organizations/security/stakeholder-access.md).
+| Category | Requirements |
+|--------------|-------------|
+| **Project access** | [Project member](../../organizations/security/add-users-team-project.md). |
+| **Permissions** | Member of the **Contributors** or [**Project Administrators**](../../organizations/security/add-users-team-project.md) group. |
+| **Access levels** | - To view or modify work items: **View work items in this node** and **Edit work items in this node** permissions set to **Allow**. By default, the **Contributors** group has this permission set. For more information, see [Set permissions and access for work tracking](../../organizations/security/set-permissions-access-work-tracking.md). |
+|**Access levels**   |To reorder a backlog or use the Forecast tool: At least **Basic** access. Users with **Stakeholder** access can't reorder backlog items or use the Forecast tool. For more information, see [Stakeholder access quick reference](../../organizations/security/stakeholder-access.md).    |
 
 ::: moniker-end
 
 ::: moniker range="< azure-devops"
 
-- **Project access**: Be a [project member](../../organizations/security/add-users-team-project.md)
-- **Permissions**: 
-  - Be a member of the **Contributors** or **Project Administrators** group. To get added, [Add users to a project or team](../../organizations/security/add-users-team-project.md) group.
-  - To view or modify work items, have your **View work items in this node** and **Edit work items in this node** permissions set to **Allow**. By default, the **Contributors** group has this permission set. For more information, see [Set permissions and access for work tracking](../../organizations/security/set-permissions-access-work-tracking.md). 
+| Category | Requirements |
+|--------------|-------------|
+| **Project access** | [Project member](../../organizations/security/add-users-team-project.md). |
+| **Permissions** | Member of the **Contributors** or [**Project Administrators**](../../organizations/security/add-users-team-project.md) group. |
+| **Access levels** | - To view or modify work items: **View work items in this node** and **Edit work items in this node** permissions set to **Allow**. By default, the **Contributors** group has this permission set. For more information, see [Set permissions and access for work tracking](../../organizations/security/set-permissions-access-work-tracking.md). |
 
 ::: moniker-end
 

docs/boards/backlogs/delete-test-artifacts.md

@@ -22,7 +22,7 @@ Test artifacts such as test plans, test suites, and test cases are all considere
 > [!IMPORTANT]
 > **Permanent and Irreversible Deletion:** Azure DevOps only supports the permanent deletion of test artifacts, including test plans, test suites, test cases, shared steps, and shared parameters. Deleted artifacts cannot be restored, and all associated child items, such as test results, are also removed. Additionally, bulk deletion of test artifacts is not supported; attempting to bulk delete results in the deletion of all other selected work items except the test artifacts.
 > 
-> **Ensure you back up any necessary information before deleting test artifacts, as this action cannot be undone.**
+> **Back up any necessary information before deleting test artifacts, as this action cannot be undone.**
 
 When you delete test artifacts, the following actions occur:
 
@@ -40,12 +40,10 @@ When you delete test artifacts, the following actions occur:
 
 ## Prerequisites
 
-- **Permissions**:
-  - To delete test runs, be a member of the **Project Administrators** group or have the project-level [**Delete test runs**](../../organizations/security/change-project-level-permissions.md) permission set to **Allow**. 
-  - To delete test plans and test suites, be a member of the **Project Administrators** group or have the Area Path node-level [**Manage test plans** or **Manage test suites**](../../organizations/security/set-permissions-access-work-tracking.md#manage-test-artifacts) permission set to **Allow**. If the user isn't part of the project administrator group, then the user must have project-level [**Delete test runs**](../../organizations/security/change-project-level-permissions.md) permission set to **Allow** along with Area Path node level permissions.
-- **Access levels**: To manage or delete test artifacts, have at least [**Basic + Test Plans**](../../organizations/security/access-levels.md) access or **Visual Studio Enterprise**. This level provides access to the full Test Plans feature set. Users with **Basic** access and with permissions to permanently delete work items and manage test artifacts can only delete orphaned test cases, which means they can delete test cases created from **Work** that aren't linked to any test plans or test suites. 
-
-::: moniker-end
+| Category | Requirements |
+|--------------|-------------|
+| **Permissions** | - To delete test runs: Member of the **Project Administrators** group or the project-level [**Delete test runs**](../../organizations/security/change-project-level-permissions.md) permission set to **Allow**. <br> - To delete test plans and test suites: Member of the **Project Administrators** group or the Area Path node-level [**Manage test plans** or **Manage test suites**](../../organizations/security/set-permissions-access-work-tracking.md#manage-test-artifacts) permission set to **Allow**. If you're not part of the project administrators group: Project-level [**Delete test runs**](../../organizations/security/change-project-level-permissions.md) permission set to **Allow** along with Area Path node level permissions. |
+| **Access levels** | To manage or delete test artifacts: At least [**Basic + Test Plans**](../../organizations/security/access-levels.md) access or **Visual Studio Enterprise**. This level provides access to the full Test Plans feature set. Users with **Basic** access and with permissions to permanently delete work items and manage test artifacts can only delete orphaned test cases, which means they can delete test cases created from **Work** that aren't linked to any test plans or test suites. |
 
 <a id="test-experience"></a>