Using Jira Planner (Data centre version) - Issues with Dependencies not moving timelines

Kevin Fotheringham

We are assessing the use of Jira planner (Data Centre) to have the project management timeline also embedded in Jira for the cross functional teams, so we can use the kanban boards as well .

The only problem preventing us using this so far is the dependency behaviour of the timeline.

If we have a task that is marked 'blocked' by a previous task, and those tasks are linked by dependency. If that previous task then takes longer to complete, and is extended, it should technically move the next task (that is linked / blocked) because it cannot start until previous task complete, but this is not the behaviour we are observing.

We only see a warning about the times, even if we then select "auto schedule", or "Review changes), the start time for the second task remains the same throughout. It does not move the secondary task start time in alignment with the new finish date of the previous task. 

Perhaps I am using the Jira Planner incorrectly, or  my expectations are different using other tools with dependency actions. 

Any help to clarify the behaviour of this would be greatly appreciated. 

Kit Friend

@Kevin Fotheringham  I started trying to replicate this (albeit in Cloud) and can't work it out either quite yet (misery loves company at least!). 

I'll keep on digging, but the learning content may give you some insights that help: https://community.atlassian.com/learning/lesson/automatically-schedule-work-with-plans-in-jira 

I checked with GPT also and I think it might be onto something if your items are scheduled into specific iterations but I didn't have time to validate in my sandbox. Might be useful as input to debug anyway!:

🧠 The Problem (Summarised)

You're expecting:

• When Task A (the blocker) is delayed,

• Task B (which is blocked by Task A) should automatically shift its start date in the timeline.

But instead:

• Jira just shows a warning, even after using “Auto-schedule” or “Review changes”,

• Task B does not move its start date.

---

🔍 Diagnosis – Why This Happens

1. Auto-scheduling in Jira Advanced Roadmaps is suggestive, not enforced by default.

• Jira will not automatically move dependent issues unless you explicitly tell it to apply the suggested changes.

• Even with Auto-schedule or Review changes enabled, you still need to accept the changes it suggests — otherwise they’re just visual suggestions.

2. Auto-scheduling needs specific preconditions to work correctly:

• The issues must have estimates (Story Points or Time estimates).

• They must be assigned to a team that has a schedule or velocity.

• The dependency type must be recognised by the scheduler (e.g., "blocks" or "is blocked by").

• The issues need to be within the scope of the plan (i.e., part of a configured issue source).

If these conditions aren’t met, Jira won’t auto-adjust the dates.

---

✅ How to Actually Make Dependent Tasks Reschedule

To get the behaviour you expect:

1. Ensure both tasks have:

   • Time estimates (e.g. 3d, 5d),

   • Team assignments,

   • Start and end dates if possible (for visualisation),

   • A valid dependency like “blocks”.

2. Go to the plan and click Auto-schedule → Review Changes

   • Jira will now suggest new dates based on dependencies and team capacity.

3. Click “Accept Changes” (or apply selectively).

   • Only then will the secondary task shift its start date.

4. Save the plan.

---

⚠️ Gotchas

• Kanban boards + Auto-scheduling: Auto-scheduling is designed with iteration-based planning in mind (like Scrum). When using Kanban, Jira struggles more with precise forecasting unless your velocity and WIP limits are configured tightly.

• Custom workflows or fields may interfere with how scheduling plays out.

---

🧭 Bottom Line

You're not doing it wrong — but Jira’s auto-scheduling isn't truly automatic in the way tools like MS Project or Smartsheet might be. It’s more of a “decision support” tool unless you take extra action to accept and apply the changes.