Move one date in Microsoft Project, and a dozen others can follow. Do the same in Jira Software, and dependent tasks usually stay where they are — even if the work blocking them has slipped by three weeks.
If you’re moving from MS Project to Jira, this is often one of the first differences you notice. Questions like “Can I get MS Project-style scheduling in Jira?” come up regularly in the Atlassian Community, but the answer depends on what you expect an auto scheduler to do.
Jira has some scheduling functionality, but it doesn’t work exactly like Microsoft Project out of the box. Jira Plans, formerly known as Advanced Roadmaps (you’ll still see “Jira Advanced Roadmaps” in older threads), includes an auto scheduler that considers team capacity and dependencies. However, it doesn’t cover every part of the scheduling process.
This post explains what auto-scheduling means, how Jira’s native tools handle it, and what you can do when you need more control over dates, dependencies, and resources.
What does auto-scheduling actually mean?
People use auto schedule to describe different things. In Microsoft Project, scheduling combines three elements that work together:
- Dependencies. Task B starts after task A finishes. If A moves, B’s dates adjust accordingly.
- Capacity. The schedule accounts for task estimates and the hours assigned resources have available. It respects each person’s working calendar, so business days, holidays, and time off affect the result.
- Constraints. Rules such as “Start No Earlier Than” or “Must Finish By” keep tasks within specific date boundaries.
Together, these rules determine when work can start, how long it should take, and what needs to happen first.
Take away one of these elements, and the schedule may no longer reflect how work can actually get done. Jira supports some of this functionality natively, but the details vary between Jira Software and Jira Plans.
1. Dependencies: Jira can show the relationship, but will it move the dates?
In Jira Software, you can link work items using relationships such as blocks / is blocked by. These links show which tasks depend on others. A timeline can display the connection, but changing the blocker’s start date or end date doesn’t automatically reschedule the blocked issue in basic Jira Software. The dates don’t flow down the chain on their own.
Jira Plans adds dependency conflict indicators. For example, it can flag a situation where a blocked task is scheduled to start before the work blocking it is finished.
But showing a conflict and resolving it automatically are two different things. You may still need to adjust the dates yourself.
This is a recurring request in the Atlassian Community. A feature request opened in 2022 asks for blocked work to shift automatically when a blocker’s end date changes. At the time of writing, the request remains in “Gathering Interest.” For teams used to Microsoft Project, this is an important difference.
It’s fair to acknowledge that not every team wants the same thing here. Some are happy to use dependencies as visual guides and move dates manually. Others expect the whole chain to react when one task slips. If that’s your case, seeing a red arrow isn’t enough.
What can help? ——> A planning timeline that supports dependency-driven date changes can reduce manual work.
For example, Planyway for Jira lets you create a dependency with a click and drag from one task to another on the timeline. The relationships are saved as standard Jira issue links, and dependent work can move when the schedule changes.
2. Capacity: what Jira’s auto scheduler takes into account
Jira Plans includes an auto scheduler, but it requires Jira Cloud Premium or Enterprise.
The scheduler uses estimates, team capacity, velocity, dependencies, priorities, and work item dates to generate a schedule.
Before you run it, there are a few details worth checking.
- Scope matters. You select the items you want to schedule. Items outside that selection can still affect the result through dependencies, priorities, and team capacity, but they won’t receive new dates from that run.
- Status matters. The scheduler schedules items in To Do or In Progress. Done items are ignored.
- Plan settings matter. You can configure which fields the auto scheduler may overwrite and whether it fills only empty fields or updates all selected fields.
- Estimates matter. The scheduler needs estimates and a consistent estimation method. Missing or inconsistent values can make the resulting schedule less useful.
This approach can work well for teams that plan around sprint velocity. It’s less straightforward if you need to understand how many hours each person can realistically work on each business day.
Outside Jira Plans, Jira Software doesn’t natively connect an issue’s estimate to an individual person’s working calendar. It can store estimates and logged time, but those values alone don’t tell you whether someone has enough available hours to finish their assigned tasks on time.
For more detailed capacity calculations, a planning app such as Planyway can help.
Its workload view compares each person’s scheduled hours with their available capacity, accounting for individual work schedules, holidays, and time off.
➡️ Try Planyway free
For example, a team member who works four hours a day shouldn’t be treated like someone available for eight. You can configure a different schedule for each user and see how much work fits into their available time.
When you place an estimated task on a person’s timeline, Planyway can calculate its dates based on that person’s working days and availability. In liquid scheduling mode, work fills each available day up to the person’s capacity before continuing to the next.
This makes it easier to understand how a schedule change affects the rest of the team, especially when people work part-time or across different locations.
3. Constraints: what happens when a date can’t move?
Dependencies explain the order of work, and capacity helps determine how much can fit into a schedule. Constraints handle another problem: some dates simply aren’t flexible.
Microsoft Project supports scheduling rules such as “Start No Earlier Than,” “Must Start On,” and “Finish No Later Than.” These rules restrict how tasks can be scheduled.
Jira doesn’t provide the same full set of scheduling constraints in its native planning tools.
You can set due dates and mark important dates with milestones, but a due date doesn’t necessarily act as a rule that automatically reschedules other work around it.
For example, a release may need to happen by the end of the month. A milestone makes that date visible to the team, but it doesn’t guarantee that every task will finish before the release.
If a date is contractual or otherwise non-negotiable, mark it clearly and check the surrounding tasks whenever the schedule changes. A timeline view can help you see dependencies, milestones, and work that overlaps with a key date. Tools such as Planyway make these relationships easier to review, although milestones themselves don’t enforce hard scheduling constraints.
How do the scheduling tools compare?
Here’s a quick comparison of Microsoft Project, Jira Software, Jira Plans, and Planyway.
Scheduling functionality | Microsoft Project | Jira Software | Jira Plans (Premium / Enterprise) | Planyway for Jira |
|---|
Dependencies | Yes | Issue links | Dependencies and conflict indicators | Dependencies displayed on a timeline |
Automatic movement of dependent tasks | Yes, according to scheduling rules | No | Don’t assume full automatic rescheduling; verify your setup | Dependent work can move when plans change |
Capacity-based scheduling | Yes | Not natively | Uses estimates, team capacity, and velocity | Workload view and task scheduling based on availability |
Individual schedules, holidays, and time off | Yes | Not natively connected to issue scheduling | Depends on the planning configuration | Configurable work schedules, holidays, and time off |
Hard scheduling constraints | Yes | Limited | Not equivalent to the full Microsoft Project model | Milestones and dates are visible but don’t enforce hard constraints |
The main difference is how these tools connect the pieces. Jira Software provides work items and links. Jira Plans adds higher-level planning and capacity-based scheduling. Planyway provides a timeline-based workflow with dependencies and more detailed workload visibility.
The right choice depends on the problem you’re trying to solve. If your team mainly needs sprint planning, Jira Plans may be enough. If the challenge is keeping dependent tasks aligned and understanding each person’s available hours, a more detailed planning setup may help.
How to set up a more reliable schedule in Jira
Regardless of which tool you use, a useful schedule starts with good data and a clear setup. These steps can help you avoid common problems.
1. Clean up your backlog
Make sure your stories, epics, and sub tasks have the estimates and date fields your planning workflow requires. Agree on one estimation method as a team — hours or story points — and check that subtasks aren’t left empty when their estimates are needed for scheduling.
If the backlog is incomplete, even a good scheduling algorithm won’t produce a reliable plan.
2. Set up working schedules and team capacity
Check the default work schedule and adjust it for part-time contracts, different working weeks, holidays, and time off. It’s worth doing at the beginning of the project, not after the first plan goes wrong.
If you use Planyway, you can configure working hours for individual team members and account for their time away. This gives you a more accurate picture of available capacity than assuming everyone works the same number of hours.
3. Make sure tasks are assigned
Capacity-based planning needs to know who is doing the work. Assign tasks to the right people so the schedule can account for their availability.
Unassigned work can still be part of the plan, but you won’t get a reliable picture of individual workload until ownership is clear.
4. Link dependencies in Jira
Create the appropriate blocks / is blocked by relationships between work items. Avoid keeping dependencies only in a spreadsheet, a separate document, or an email thread.
Jira links provide a shared source of information. Planning tools that read these links can use them to display dependencies and help you understand how changes affect the schedule.
5. Configure the scheduler before running it
If you’re using Jira Plans, review the plan settings before running the auto scheduler. Check which items are included, which fields it can overwrite, and whether it should fill empty dates or replace existing ones.
If you’re unfamiliar with the setup, run the scheduler on a copy of the plan first. Check the resulting dates and conflicts before you call the schedule ready and save changes to your working plan.
6. Plan in a timeline view
Editing start and end dates in individual issues can be slow when many tasks need to move. A timeline makes it easier to see the sequence of work, adjust dates, and understand how tasks relate to one another. Moving things around and seeing the effect straight away is also how most people learn how their plan really works.
In Planyway, you can create dependencies, move tasks, and review team workload in the context of the schedule instead of switching between separate screens.
7. Mark fixed dates and check for conflicts
Use milestones for releases, launches, and other important dates. After a significant schedule change, check dependencies, workload, and the tasks leading up to those milestones.
A sudden increase in someone’s scheduled hours or a dependency conflict can be a sign that the plan needs attention.
Choose the scheduling setup that fits your team
Jira can handle many parts of project planning, but the level of automation depends on which tools you use and how your plan is configured.
If your team works in sprints and plans around velocity, Jira Plans may cover most of what you need. If you need to see how individual working hours affect dates, or want dependent tasks to move when plans change, you may need an additional planning layer.
The most important thing is to understand what your scheduler actually does before relying on its dates. Check the estimates, assignments, dependencies, and working calendars, then test how the plan responds when something changes.
Want more posts on planning in Jira? Read our guides on capacity planning and resource planning.
And if you’ve found a way to get MS Project-style scheduling working in Jira, share your setup in the comments. It would be useful to hear which approaches work best for different teams.
