Automation to update start and end dates of linked issues

[TomT]

I have issues that are blocked by other issues and linked them trough the timeline board.

If there is a delay for some reason on the first issue I will drag the due date, let's say 5 days, in the future. But the linked/blocked stories do not move along.
I want the linked/blocked issues to move with the same amount of days as the first issue. 

This way we can track what the changes mean for the completion date of all linked issues.

I know this is not a function out of the box so I am trying to solve it using automation. 

But I already get stuck quite quickly, even after looking at the examples here at the site.

Can someone help me forward?

[John Funk]

Hi Tom - Welcome to the Atlassian Community!

Can you share the details of the Edit Issue for the Start date field? 

Also, what is not working with it? 

[TomT]

Please see my reaction to Marco above. 

[John Funk]

So you run the rule and the Start and End dates move? Or Just the End date? 

[TomT]

Only the end date moves.

[John Funk]

Okay, that's very weird. I would have to see more screenshots of the history, audit log,  and all that to be able to tell more. 

[TomT]

I made the date in the automation to move the start to august 18 and started with the timeline below.

Then I moved the second to last issues end date from august 7 to august 8. 

After a second it changes to the screen below.

[TomT]

No ideas?

[John Funk]

Sorry, I really don't. I would open a support ticket with Atlassian. 

[Marco Brundel]

Hi @TomT ,

What have you set up behind the Start Date field? Did you use a smart-value there to copy Due date?

Regards, Marco

[TomT]

Just to test I currently have a fixed date there. 

I would want to place a smart value there meaning, the difference in days to the other issues end date has moved, is added to the start date.

But if I run this now for some reason my end date moves.... 

[Marco Brundel]

Hi @TomT ,

What does the audit log indicate in the automation rule, has the issue changed as you expect? And if you look in the history of the changed issue, can you find out why the end date was changed?

groeten, Marco

[TomT]

Audit log is below. No it the result is not as expected. 
The end date moves instead of the start date. 

[Neda Khavari]

Hi All,

I have the automation works for updating start & due date of blocked tasks, but the automation doesn't work on cascading issue.

Any idea on how to resolve this issue?

[V-Guard R_D Elec_]

Hi @Ste Wright ,

Thank you for this rule; it works for me.

The only issue I'm facing now is that it doesn't work for cascading issues.

For example, let's consider the scenario where A blocks B, and B blocks C. With this rule, only issue B is updated when the due date of A changes. However, this rule does not work for issue C.
Could you please let me know if there is any option to overcome this scenario?
Best Regards,
Alias Paul

[Ste Wright]

Hi @TomT 

I couldn't get this to work using smart values for the standard Start Date field - it clears it before setting it again, regardless of how I do it. I could do it using End Date though (as you mentioned above)

So I created a workaround using additional fields...

---

Setup

• Create a new custom date picker field - eg. Current Start Date
• Create additional custom date picker fields per field needed - eg. Current End Date
• Either leave these off your screens, or add them to a view-only screen (via screen scheme issue operations)

---

Rule

• Trigger: Field Value Changed
  • Field = Due Date
• Action: Create Variable
  • Name = DaysAdded
  • Smart Value = {{fieldChange.from.toDate.diff(fieldChange.to.toDate).days}}
• Branch: Related Issues
  • Type = Linked Issues
  • Link Type = blocks
    • Branch-Action: Edit Issue
      • Field = Current Start Date
        • Action = COPY (via 3-dots icon)
          • Issue to Copy From = Current Issue
          • Field to Copy from = Start Date
      • Field = Current End Date
        • Action = COPY (via 3-dots icon)
          • Issue to Copy From = Current Issue
          • Field to Copy from = End Date
    • Branch-Action: Re-fetch issue data
    • Branch-Action: Edit Issue
      • Field = Start Date
        • Value = {{issue.Current Start Date.plusDays(DaysAdded.asNumber)}}
      • Field = End Date
        • Value = {{issue.Current End Date.plusDays(DaysAdded.asNumber)}}
    • Branch-Action: Re-fetch issue data
    • Branch-Action: Edit Issue
      • Field = Current Start Date
        • Value = NULL (empty)
      • Field = Current End Date
        • Value = NULL (empty)

---

Notes:

• You could use a combination of the End Date as a smart value, and Start Date with the field if preferred
• The "Re-fetch issue data" help to ensure the rule runs in sequence
• I've cleared the "Current" date fields once the copy is complete, so these aren't populated unnecessarily

---

Let us know if this workaround works for you!

I'd also encourage reporting the Start Date issue to Atlassian, it might be a bug with that custom field (which is Atlassian-created).

Ste

[Patrick FG]

@Ste Wright thanks for the insight as I have been trying to do something similar.

Essentially on the advanced roadmaps I would like to make an automation so that when one issue is linked, the next issue cannot start until this one is finished. I then want all the linked issues are pushed out automatically by the same amount of delay. This automation would mimic a default Gantt Chart behavior.

I tried to follow your solution but maybe my Jira interface is different because I can't replicate your solution. 

[Ste Wright]

Hi @Patrick FG 

Are you on Cloud or Server/DC?

Ste

[Patrick FG]

Cloud

[Patrick FG]

hi @Ste Wright , 

Here is my screen shot that I made out from your instructions. We are on the cloud service.

[Ste Wright]

Hi @Patrick FG 

Does the rule error? Is there anything in the audit log in terms of details?

It's difficult to know what might be inaccurate without seeing more specifics within each step.

Ste

[Ahmad Khamash]

Hi Ste Wright 

Thank you for the solution provided, 

I have been trying the same thing worked for me, yet it does not work on cascading issues ( multiple blocked issues, ) 
reference below : 

On changing issue #1 rules works perfect on Issue #2, Yet does not follow to Issue #3 


Did you face this issue, 
Note: I'm on cloud. 

[Ian Lucas]

Hi, im interested to see if there was a final resolution which worked for everyone? I am about to try and test this myself.