Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Is a dependent issue scheduled one day later automatically?

I have an issue A which has an estimate of 2 hours and and issue B which has an estimate of 2 hours. The team the work is connected to has enough capacity to do the work.

When I add an dependency (Issue B is depependent on Issue A), Issue B is scheduled ONE DAY LATER (visually "behind on the same level" as Issue A), although there should be enough capacity for Issue B on the day where Issue A is scheduled I would have assumed (which would mean for me a visual representaton "below" Issue A on the same day.)

Can somebody explain this behaviour? Does a dependency always mean, the issue can only be started the next day? Or what am I missing?

Thanks for your help!

1 answer

1 accepted

0 votes
Answer accepted
Thomas
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 04, 2018

Hi @Sascha Heckelei,

 

By default dependencies must happen on a different time unit (Different sprint for Scrum teams, different day for Kanban teams).

The main reason is that Portfolio does not schedule below that time unit, so as far as Portfolio is concerned this issue won't be done until the end of the day which means dependent items can only start as early as the next day.

You can change this behavior in your plan configuration -> Scheduling -> Dependent story constraint

You can read more about it in the docs here

 

Cheers,

Thomas

Thanks @Thomas for the clarification! 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events