---
title: "Monitor work item mapping"
slug: "monitor-work-item-mapping"
description: "Monitor Azure DevOps work items, their mappings, relations, and synchronization history with detailed insights and conflict resolution steps."
tags: ["Task", "RapidValue", "RV"]
updated: 2026-03-20T13:42:06Z
published: 2026-03-20T17:46:36Z
canonical: "docs.staedean.com/monitor-work-item-mapping"
---

> ## 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.

# Monitor work item mapping

If you have synchronized with Azure DevOps, you can monitor the mapped work item information, with its mapped entities, related work items, and synchronization history.

### Steps

1. Go to **RapidValue** > **Inquiries** > **Work item**.

> [!NOTE]
> Note
> 
> You can also open the work item mapping info for a mapped RapidValue entity. Go to the **RapidValue entity** page, select the desired record, and click **DevOps**, **Work item**.
2. In the list, find and select the desired record.
3. In the list, click the link in the selected row.
4. On the **Details** tab, you can review: - The general information of a work item. For example, if it is mapped or unmapped. - The RapidValue entities to which the work item is mapped. A work item can be mapped to several RapidValue entities. Only one of these can be the primary mapped entity.
5. You can review the work items that are related to the current work item in DevOps. You can have several types of related work items:

Click the **Relations** tab.

> [!NOTE]
> Note
> 
> To view a related work item in DevOps, select the relation, and click **Open in DevOp**s
  - Parent (only once)
  - Child
  - Link
6. You can monitor the synchronization history of each work item that is currently mapped or that was mapped previously.

For each synchronization that is done, the updates that are done are logged in this history.

On synchronize, three values play a role: DevOps value, RapidValue value, and the latest logged New value for the entity. If the direction is:

Click the **History** tab.

> [!NOTE]
> Note
> 
> In case of a conflict, the original values are saved in the New value field and Old value field. Which value is shown in which field depends on the direction.

To solve the conflict, you can manually repair the value. You can do so, as desired, in either **RapidValue** or **DevOps**.
  - 'In' and the DevOps value differs from the latest logged New value, the RapidValue value is updated with the DevOps value and this change is logged in the work item history. If the original RapidValue value also differs from the latest logged New value, the logged change is marked as a 'Conflict'.
  - 'Out' and the RapidValue value differs from the latest logged value, the DevOps value is updated with the RapidValue value and this change is logged in the work item history. If the original DevOps value also differs from the latest logged New value, the logged change is marked as a 'Conflict'.
7. Close the page.

## Related

- [Use Azure DevOps integration](/use-azure-devops-integration.md)