Why are all schedule bars are the same length despite different time estimates

[Jarrod Smith]

The three tasks below all have the same length schedule bar, yet each task has a different time estimate (1w, 3d, 1d). Why is this?

[Alex Koxaras _Relational_ · Accepted solution]

Hi @Jarrod Smith and welcome,

Most likely you have set the start and due date to be the same. Estimates do not affect the start and due date.

[Jarrod Smith]

Thanks @Alex Koxaras _Relational_. Do you mean the start and due date of the task, sprint or epic?

Currently the tasks have only the "Original estimate" field.
The epic has a start date of 1st Sep and no due date.
The sprint is set to 15-29 Sep.

What should I change to fix it?

[Alex Koxaras _Relational_]

@Jarrod Smith it seems that I've made a mistake. I tested it myself, and even if you add start and due date, it seems that a task will take the duration of the sprint. I haven't figured out a way to change how it looks on the roadmap

[Jarrod Smith]

Okay thank you for looking into it @Alex Koxaras _Relational_

[Jessica Tran]

Hi, @Jarrod Smith currently on Roadmaps the child issue bars will be visualised to take on the length of its assigned sprint, i.e. the sprint's start date and end date, and this cannot be customised.

However, there are some discussions to better support Kanban projects Date range for child issues on roadmap

[Rathesh Richards]

Kanban projects are now supported - More here: https://community.atlassian.com/t5/Jira-Software-articles/What-s-new-in-the-Roadmap-view-I-m-so-glad-you-asked/ba-p/2077594