---
title: "Manually map business process to Azure DevOps work item"
slug: "manually-map-business-process-to-azure-devops-work-item"
description: "Learn how to manually map a business process to Azure DevOps work items, including steps for mapping, unmapping, and synchronizing processes effectively."
tags: ["Task", "RapidValue", "RV"]
updated: 2026-03-20T10:28:52Z
published: 2026-03-20T17:46:36Z
canonical: "docs.staedean.com/manually-map-business-process-to-azure-devops-work-item"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Manually map business process to Azure DevOps work item

You can manually map a business process to an Azure DevOps work item. For example, if a relevant work item already exists in the DevOps project or if you have made some changes in the business process hierarchy and the mapping is undone, or if you have earlier unmapped the requirement.

### Steps

1. Click **Business process modeling**.
2. Click the **Business processes** tab.
3. In the tree, select 'a business process'.
4. Click **DevOps**.
5. Click **Map** to DevOps.
6. Sub-task: Map to not mapped work item in DevOps project.
  1. In the **Work item ID** field, type a value.

> [!NOTE]
> Note
> 
> Copy the work item ID from DevOps and paste in in this field.
  2. Check if the work item exists in the connected DevOps project. If **OK**, the name and description are copied from the work item.

Click **Check**.
7. Sub-task: Map to an already mapped work item.
  1. In the **Existing work item** section, select the desired work item.

> [!NOTE]
> Note
> 
> On selection, the work item ID, name, and description are filled in the upper section of the dialog.
8. Click **OK**.

> [!NOTE]
> Notes
> 
> You can also unmap a business process from a DevOps work item. To do so, select the business process, and click **DevOps**, Unmap.
> 
> When you again synchronize the business process, a new work item is created for the business process. Note that the original work item also stays in the DevOps project. This can result in an issue with the Parent link in DevOps. If you do not want a new work item created, you can manually map the business process again to the original work item.

## Related

- [Synchronize RapidValue with Azure DevOps](/synchronize-rapidvalue-with-azure-devops.md)