---
title: "Move version on another board"
canonical: "https://help.releasemanagement.app/space/RM4J/3092774920/Move%20version%20on%20another%20board"
format: markdown
---
> Macro (include)

# Topics

> Macro (toc)

# Step 1: Obtain Token

Go to [https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081347#How-I-can-get-a-Token-to-access-API?](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081347#How-I-can-get-a-Token-to-access-API?) section to learn how to generate token and [https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081347#How-to-execute-calls-to-our-APIs?](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081347#How-to-execute-calls-to-our-APIs?) section to learn how to make calls to our Rest API.

> ℹ️ Find out more about personalized tokens here [https://confluence.atlassian.com/enterprise/using-personal-access-tokens-1026032365.html](https://confluence.atlassian.com/enterprise/using-personal-access-tokens-1026032365.html).

# Step 2: Find out some properties you would need

In this example, we will be updating the versions on a board (source board), and that update will result in a version update on another board (destination board).

Also, we would need to obtain Source and Destination board IDs and create a mapping to column ID between source and destination boards.

## Obtain data from the Source Board

Open board ID and copy board ID:

![image](media://129e00b0-0f4b-4562-befc-d080b00eb326)

.. and click on API icon:

![image](media://413c55d9-8393-46ec-9e2b-3d0318fc166d)

Find board by ID endpoint:

![image](media://877a4e97-478d-4bf0-95f3-2a339f16de05)

Past BoardID copied above and run it.

In response, you will get a collection of columns and versions associated with it.

Please extract all column IDs that should participate in the synchronization.

![image](media://d0d31427-5be9-4fb2-85ad-60f3d8ccd4f2)

 

We recommend using a mapping table to make it more obvious.

Example of the table:

| **Source Status Name** | **Source Board  Status Id** | **Destination Status Name** | **Destination Board  Status Id** |
| --- | --- | --- | --- |
| **New** | 1600 |  |  |
| **Planning** | 1603 |  |  |
| **Dev** | 1601 |  |  |
| **STG** | 1604 |  |  |
| **UAT** | 1605 |  |  |
| **Done** | 1602 |  |  |

## Obtain data from the Destination Board

Please repeat the same steps on the destination board.

As a result, we should receive the destination board ID (for instance 530) and complete the status mapping table. For instance like this one:

| **Source Status name** | **Source Board  Status Id** | **Destination Status Name** | **Destination Board  Status Id** |
| --- | --- | --- | --- |
| **New** | 1600 | **Todo** | 1617 |
| **Planning** | 1603 | **In progress** | 1618 |
| **Dev** | 1601 | **In progress** | 1618 |
| **STG** | 1604 | **UAT** | 1620 |
| **UAT** | 1605 | **CAB** | 1621 |
| **Done** | 1602 | **Done** | 1619 |

# Step 3: Hooks Configuration

Open Source board and for each status in the status mapping table repeat the following steps

> ℹ️ The hook could be created once and after that cloned
> ℹ️ 
> ℹ️ ![image-20241022-093950.png](media://e02a8c57-1199-4b7a-9621-a46958fba72c)

Create new hook

![image-20241022-094045.png](media://95f8a945-851c-4462-8375-7549762fa419)

 

![image-20241022-094310.png](media://de80f96c-2bb4-42a2-84c9-c05eb7bb4b1a)

Add the following parameters to the hook configuration:

**URL: **<https://<YOUR_JIRA_HOST>/rest/release-management/1.0/board/<destination_board_id>/version/{{entity.id}}/move>

- *<YOUR_JIRA_HOST> *to be replaced with your Jira host URL
- *<destination_board_id>* will be replaced with your destination board ID. In our demo case, it should be 530

**Method: **<PUT>

**Request body:**

```
{
"columnId" : <destination_column_id>,
"afterVersionId" : null,
"virtualVersion":false
}
```

where <`destination_column_id`> is the column ID from the mapping table on the destination board


Open the Headers Tab and add:

- **Content-type:** application/json
- **Authorization:** Bearer  <YOUR_TOKEN_FROM_PREREQUISITES>

![image-20241022-100102.png](media://ad16a008-3de0-4b06-b10a-32605da94cc1)


> ⚠️ The token is sensitive information so please make sure that a limited amount of people will have access to the board settings

Please repeat the same steps for other statuses or use the **Clone** to clone created hooks

# Step 4: Test it!

As soon as the configuration is ready, please try to move the version on the board and check that the Hook is executed without any errors:


![image-20241022-100642.png](media://54f54a35-4bb2-48d0-b830-ad689b49a8cf)

> Macro (include)