Hi @Dean Milenkovic
You'll need to use a Global Automation rule for this - you'll need to be at least a Product Admin to create these, then go to:
- Settings (cog icon in top-right) > System
- Select Global automation from the left-hand side
---
You can use a Branch in your rule to refer to another issue as the receiver of the action. Which Branch you need depends on the best option to locate the second issue - eg.
- Is the second issue a child or parent of the first one? There's branches for these
- Are the two issues linked? You could use that branch type if yes
- You can also use JQL to locate another issue as part of a branch if needed
---
The rule then might look like this...
- Trigger: Field Value Changed
- Field to Monitor = Due Date
- Condition: Issue Fields Condition
- Field = Project
- Condition = equals
- Value = Project 1
- Condition: Issue Fields Condition
- Field = Summary
- Condition = contains
- Value = Words Here
- Create Variable:
- Name = previousDate
- Smart Value = {{changelog.dueDate.fromString}}
- Create Variable:
- Name = currentDate
- Smart Value = {{changelog.dueDate.toString}}
- Create Variable:
- Name = daysDiff
- Smart Value = {{previousDate.toDate.diff(currentDate.toDate).days}}
- Branch: Related Issues
- Type = Type Here
- Branch-Action: Edit Issue
- Field = Due Date
- Value = {{#issue.dueDate}}func=plusDays({{daysDiff}}) {{/}}
---
A few notes on this rule...
- This rule uses smart values to...
- Locate the previous and current due dates of the trigger issue
- Calculate the difference in days
- Add that number of days to the related issue
---
Let us know if this works for you!
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.