Manage Priority of cloned issue

[Omkar Rajale]

I am cloning an issue using the clone functionality. And an automation is running that is check if the cloned issue has particular fields(ex. due date) and clears them. Additionally I have an automation that sets due date based on priority. And Priority has four values high , normal , medium , low also there is no null or empty value for this field. 

There can be two scenarios:

1) Cloned issue can have the same priority as the original one and user did not update this field. Automation will clear the old due date set the new due date based on the created date.

2) Cloned issue can have different priority , user will update this field after cloning. Automation will trigger and update due date based on the new priority value.

How do I achieve this. 

[Ashok Shembde]

Hi @Omkar Rajale ,

In this scenario, you can set up two automations.

1. Clear Due Date on Clone

1. Trigger: Issue Created

2. Condition: Issue Type = your relevant issue type (optional filter)

3. Action:

   1. Edit issue fields → set Due Date = null

4. This ensures cloned issues start with a clean Due Date.

2.Set Due Date Based on Priority

1. Trigger:

   1. Option 1 : Field value changed → Field: Priority

   2. Option 2 : Issue Created OR Field value changed (Priority)

2. Condition (optional but safe):

   1. Due Date = empty

3. Action:

   1. Use an "If-Else block" to define Due Date logic

This works as per your expectation.

[Omkar Rajale]

ok will check this let you know

[Omkar Rajale]

Thanks @Ashok Shembde , It worked.