Hello @Jessica Hu
Welcome to the Atlassian community.
That is not a native feature of a Standard subscription of Jira.
In the Premium subscription there is an "auto-schedule" feature but is only within the Plans (aka Advanced Roadmaps) feature and it doesn't operate in the way you describe.
If you want dates to be updated automatically you need either a third party app from the Marketplace or you develop your own work around.
I wrote an article about using Automation Rules (now Flows) for a work around. You can find that article here.
Updating dependent task's dates when predecessor task date changes
Hi Jessica @Jessica Hu -
Trudy is right, I will just add the part that usually bites people a few months in.
The reason the setting does not exist is architectural. What you want is ascheduling engine: predecessor moves, successor recalculates. What Jira gives youis link types. "Blocks / is blocked by" is a semantic label for humans and JQL - itcarries no scheduling meaning. There is no duration behind it, no lag, nofinish-to-start constraint. So there is nothing for Jira to recalculate. It is nothidden somewhere in settings, it was never built into Jira Software.
The Automation/Flows workaround Trudy linked is the right first step for a simplechain. Worth knowing where it stops holding, so it does not surprise you later:
- working calendar: a rule that adds days to a date will happily land a start dateon a Saturday or in the middle of someone's PTO, unless you code the calendaryourself- duration: pushing a start date does not preserve the length of the task, so thefinish has to move too, and then everything downstream of it- multiple predecessors: a task blocked by three tasks must start after the LATESTof them finishes. Per-link rules tend to react to whichever one moved last- cascades: a change three levels up should ripple all the way down, which meansrules triggering rules, and Jira's loop protection will stop the chain before yourplan does
None of that means do not try it. It means you are hand-building a scheduler out ofautomation rules, and somewhere past 20-30 linked tasks the maintenance becomes itsown project.
Disclosure so you can weigh this properly: I work with Be on Time, an AtlassianMarketplace partner. We build MSP Planner for Jira, which exists for exactly thisgap - real FS/SS/FF/SF dependencies with lag, task durations, working calendars,critical path, writing dates back to Jira issues. There are several Gantt/schedulingapps in this category on the Marketplace, ours is one of them.
https://marketplace.atlassian.com/apps/3162894022/msp-planner-for-jira
If your chains are short, honestly - start with Trudy's Flows approach. It is free.
It looks like you're new here. Sign in or register to get started.
