---
title: "Update Jira issue due date with the Version milestone due date"
canonical: "https://help.releasemanagement.app/space/RMC/3101097985/Update%20Jira%20issue%20due%20date%20with%20the%20Version%20milestone%20due%20date"
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

In the below use case, we would need to update some Jira issues with the data that will be received from the version milestone called “*Due Date*”

# Prerequisites

# Step 1: Obtain Prerequisites

As usual we would need a BoardID and an API token.

**Obtain Board ID:**

![image](media://0c881ad8-a54c-48e5-8284-fb73e272f2e6)

**Obtain API Access Token**

[https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/3168108545](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/3168108545) 

# Step 2: Create Jira Automation rule to update Jira issues

Create Jira Automation rule

Add trigger by incoming webhook with the following configuration and store the webhook URL: 

![image-20251113-134418.png](media://91e8a36d-7c31-4727-8a7d-92596183c3ba)

Execute webhook to get milestones

**URL:** <https://rmcloud-prd.releasemanagement.app/api/1/board/<YOUR_BOARD_ID>/version/{{webhookData.entityId}}/milestone>

> ℹ️ Replace <YOUR_BOARD_ID> with your board ID from the prerequisites

**Method:** GET

**Headers: **Open Headers and add header

> ***X-RM-Token:**** <personal_token_body>*

> ⚠️ At the same time, the Authorization header should be removed from the request if used.

![image-20251113-134531.png](media://b85c1ec4-2c37-4d0c-b59b-6109eeb4a88c)

Add For Each Branch action

**Smart value: **{{webResponse.body}}

**Variable Name:** milestoneObject

![image-20241212-160037.png](media://97fb50fe-179c-41f3-a78b-48b0224ca08f)

Add If condition to find a milestone with a name that contains “*Due Date*“

> ℹ️ … or any other condition what matters to your use case!

**First value:** {{milestoneObject.name}}

**Condition: **Contains

**Second value:** *Due Date*

![image-20241212-160227.png](media://579cb0e8-d77f-4291-a514-a9ea0e51299f)

> ⚠️ <u>**Add as a next action that needs to be done with the issue. For instance update of some fields or similar**</u>
> ⚠️ 
> ⚠️ - Note: that in that case, we would need to use API call to Jira as Jira automation doesn't support issue look-up inside the loop
> ⚠️ - The alternative solution is to get milestones by index and iterating issues instead.

# Step 3: Create Release Automation rule to to trigger Jira Automation on milestone date change

Open board settings 

Navigate to automation and create a new Rule

Define a rule name and define a trigger. For instance “*Milestone date changed*“

![image-20241212-160516.png](media://f032567d-07a6-4d08-9cf1-ba1dbd99c1b2)

Add action “Invoke Jira Automation“

Define name. Paste as a URL from the Jira Automation Webhook that we created in the previous chapter

> 📝 Due to recent change you would also need to copy a **Secret Key** in addition to URL.

![image-20241212-160624.png](media://a1dbfdc4-8e03-46ea-a6b2-157578649b3a)

> Macro (include)