nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Jarrod Smith_ucgvi3

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?

Accepted answers

Alex Koxaras -Relational-

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.

All comments

Alex Koxaras -Relational-

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_ucgvi3

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_ucgvi3

Okay thank you for looking into it @Alex Koxaras -Relational-

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

roadmap

atl-roadmap