---
title: "Update version status in Release Management with Jira issue status update"
canonical: "https://help.releasemanagement.app/space/RM4J/3092611531/Update%20version%20status%20in%20Release%20Management%20with%20Jira%20issue%20status%20update"
format: markdown
---
> Macro (include)

# Topics

> Macro (toc)

# Introduction

Let’s create an automation to move version in progress at least one issue gets in progress.

# Step 1: Generate 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 (e.g. destination ColumnID)

If you want to move version into certain column upon issues status update you would need to know **destination column id**. You would need to use our [https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081347](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081347) to get it.

Please copy board ID:

![image](media://e37cf76c-c036-45b8-918b-466b9a4702d7)

.. and click on API icon:

![image](media://65d3c283-8b60-49fc-a15c-70e9f64a8921)

Find board by ID endpoint:

![image](media://5f5d0a9b-f8b8-4b62-9603-1db28feaf4af)

Past BoardID copied above and execute it.

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

Please find the column you need and copy ColumnID:

![image](media://be2c7bb0-a99d-4e04-b153-3fd74a81bae6)

# Step 3: Create rule with Jira Automation 

Go to your **Project Settings**, select **Automation** and **Create rule**.

![image](media://28fbecde-3e24-4a43-840f-88b7a96bc02c)

For our use case we will use **Issue transitioned** trigger.

![image](media://fb729811-0d8f-40ed-902a-5e789ad318fb)

Select appropriate statuses and save it.

![image](media://30d7df9f-4d32-403e-bf19-36db76600531)

Now we would need to add New Action - **Send Web Request**

![image](media://2caa18cc-fe6b-4fc5-a3bc-1fcf59962bfb)

**URL: **<https://demo.releasemanagement.app/rest/release-management/1.0//board/**BoardID**/version/**{{issue.fixVersions.id}}**/move>

**Header: **<Name: Authorization, Value: <u><span style="color: #bf2600">**Bearer**</span></u> *Your Personalized Token*>

**Method:** <PUT>

**Request Body:** <Custom data: **{"columnId": DestinationColumnID}**>

![image](media://f413722f-15e9-4dc1-8192-86275db8b951)

Almost there - put a name & click “**Turn on**“ rule.

# Step 4: Test it out

We have version in **To-do** column.

![image](media://e6b97344-1609-49f6-99b0-094d8b05a74f)

With all the issue in **To-do** status.

![image](media://0d986d1d-f234-4cec-9b36-fff94cf0ec4d)

Let’s change status of one issues to **Sprint-development**

![image](media://36cf89c6-24f5-4ae9-a2e2-c77efe47781d)

As a result the version was moved to Sprint Development column.

![image](media://5baaa5e4-43ef-4749-b893-698e4aeb1e08)

Let’s check the audit log of the **rule.**

![image](media://7bad1c2f-a161-411d-95e0-527d666bc102)

Enjoy it!

This is the use case of creating Package, putting it in specific Column and assigning Tag to it. Why it’s important? - It shows how you can create multiple actions with Jira Automation and connect execution of one action with another.

> Macro (include)