---
title: "Board Sync: Update version property while version move on another Board"
canonical: "https://help.releasemanagement.app/space/RMC/3112108061/Board%20Sync%3A%20Update%20version%20property%20while%20version%20move%20on%20another%20Board"
format: markdown
---
> Macro (include)
# Troubleshooting?
> ℹ️ Have issues running Release Automation rules? Please check our troubleshooting guide - [https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/2522284033/Release+Automation+for+Jira+Triggers+Conditions+Actions#%F0%9F%86%98-Troubleshooting-Automation-Rules](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/2522284033/Release+Automation+for+Jira+Triggers+Conditions+Actions#%F0%9F%86%98-Troubleshooting-Automation-Rules).
# Topics
> Macro (toc)
# Introduction
**Use case**: I would like to update version properties on one board based on property values on another board and triggered by moving the version on another board
# Step 1: Obtain Prerequisites
The board initiating the synchronization will be referred to as the "Original Board," while the board to be updated will be called the "Destination Board."
**Obtain ****Destination Board ID****:**
**Obtain ****Property IDs ****and property ****option IDs**** from the Destination Board**
Execute the Get Board method from the API tab on the Destination Board :
Locate properties inventory that is called **customFields** collection:
Extract all needed properties IDs for needed values including options IDs for multi and single select fields.
***Example:***
| ***Property: “Risk level”*** | ***Property: “Risk Description”*** |
| --- | --- |
| ***Property ID:**** *`66fe75d24g79c1f34935706f`
***Property type****: Single select*
***Options:***
- *Low: - ID: *`66fe13d497179b971da9b565`
- *Medium: - ID: *`66f173d234c74c7f445367070`
- *High:- ID: *`61fe72e137149b861d73b566` | ***Property ID:**** *`66f878d26g74c1f24935706f`
***Property type****: String*
***Options:***
*Not applicable for string* |
**Obtain API Access Token:**
[https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/3168108545](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/3168108545)
# Disclaimer: Complexity !!!
> ℹ️ If a simple property requires synchronization, it can be handled directly through Release Management automation.
> ℹ️
> ℹ️ However, for more complex properties, such as Single Select or Multiselect fields, a lookup table is necessary to map property IDs between boards. As this capability is not yet supported in Release Management automation, Jira automation must be used to achieve this.
> ℹ️
> ℹ️ In this example, we will demonstrate a solution for synchronizing complex properties.
In this example, we aim to update the same version on the Destination Board when the version is moved to the "In Progress" status on the Original Board. Additionally, the Single Select property "*Risk Level*" and the string property "*Risk Description*" will be transferred from the Original Board to the Destination Board.
# Step 2: Create a Jira Automation rule to execute the update
Open any project and in the project settings add new Jira automation
**Add “Incoming Webhook“ trigger**
Configure it like on the picture and copy the URL
Save the URL as it we will be used in the next steps.
**Create a variable “Risk Level“**
Let's create a variable Risk level that will be used to store the value from “Risk level” on the Original board. This will simplify the variable usage in the next steps.
Create a variable with the following configuration:
- ***Variable name*****:** riskLevel
- ***Smart Value:***** **{{webhookData.Risk Level}}
**Create a variable Risk Description **
Actually for the same purpose.
- ***Variable name*****:** riskDescription
- ***Smart Value*****: **{{webhookData.Risk Description}}
**Add “Create Lookup table” action**
This step involves defining a mapping between field option IDs for the Original and Destination Boards. Mapping is necessary when using Single or Multiselect fields. However, for plain fields such as number, user, multi-user, string, date, or date-time fields, no mapping is required.
Set the following values
- ***Lookup table variable name:***** **valuesTable
- ***Values***
| ***Key*** | ***Value*** |
| --- | --- |
| Text Value from the single/multi-select field:
**ID** from the destination board | The values are prepared in prerequisites |
| Text Value from the single/multi-select field:
**ID** from the destination board | The values are prepared in prerequisites |
***Example****:*
**Update “Risk Level“multi-select variable**
Add “Send Web Request“ action
***Web request URL****: <*https://rmcloud.releasemanagement.app/api/1/board//version/{{webhookData.entityId}}/customField>
***Method****: *
***Enable option****: *
***Payload****: *
```json
{"":"{{valuesTable.get(riskLevel)}}"}
```
where ******* *is the destination board property ID from the prerequisites section
***Headers: ***Open Headers and add header
> ***X-RM-Token:**** *
> ⚠️ At the same time, the Authorization header should be removed from the request if used.
***Example****:*
**Update “Risk Description“ String field **
Add “Send Web Request“ action
***Web request URL****: <*https://rmcloud.releasemanagement.app/api/1/board//version/{{webhookData.entityId}}/customField>
***Method****: <*PUT>
***Enable option****:* Delay execution of subsequent rule actions until we've received a response for this web request
***Payload****: *
```json
{"":"{{riskDescription}}"}
```
where ******* *is the destination board property ID from the prerequisites section
***Headers: ***Open Headers and add header
> ***X-RM-Token:**** *
> ⚠️ At the same time, the Authorization header should be removed from the request if used.
***Example****:*
# Step 3: Create an Automation rule on the Original Board and connect it to the Jira Automation rule
Open the Original board and create an automation rule:
Fill the data line on the screen and add a condition
Add Field condition:
And select the status that should be used for triggering the rule. In our case “In progress“
Add Invoke Jira Automation Action action with the following settings:
> 📝 As of rest change you would also need to cope a **Secret Key** in addition to URL.
Save the Rule.
# Step 4: Test it
Test it by moving the version to the needed column on the original board
Check result:
Open Jira automation rule and check the result:
> Macro (include)