How to make successor respond to predecessor's schedule change?

[Dominik_Garstka]

Can you give a simple walk through on how to do this basic thing? When predecessor takes longer, all chain of tasks behind it moves out.

[Jack Brickey]

Hi @Dominik_Garstka , welcome to the community.

So my first question is, how are you defining predecessors and successors? Are you linking issues like finish to start? If you are using links to define this than the way to adjust dates is by using automation. The other question is when you refer to something moving out does this imply that you have a start date to the due date of the predecessor or Maybe you want to change the due date of the successor by the equal amount of the slip date of the predecessor?

[Trudy Claspill]

Adding to this...

If you

1. use issue linking to identify predecessor and successor task
2. are linking issues finish-to-start

...then you may find this article I wrote to be helpful.

Updating dependent task's dates when predecessor task date changes 

[Dominik_Garstka]

Thanks for quick reply Jack. My question was in context of Plans/Timeline. I'm after most basic FS dependency - if A is predecessor of B, I want B start to move automatically is A's finish date moves. 

[Trudy Claspill]

The Plans feature does not provide that sort of date shifting automatically. It has a Scheduling feature, but that is not going to meet your requirement.

Jira does not otherwise provide a native date shifting feature. The solution has to be customization, either using something like I described in my article (linked above) or looking at third party apps.