The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Broken dependencies even though concurrency is allowed

Ronald Galea
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 17, 2025

In some cases (see below), dependencies are marked as broken even though the settings allow concurrent dependencies.

Settings/Context: concurrent dependencies are allowed:

concurrent_deps.png

Problem: The following example shows 3 issues, all with the exact same start and end dates. In one case, the dependency is fine, the other is red (broken):
unexpected_broken_dep.png

The difference is:

- the blocking issue in the red case has rolled up dates

- the blocking issue in the ok case has manually specified dates

This looks unexpected since the concurrency setting specifically states that it applies to auto-scheduled issues too.

 

Thank you!

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Ofir Oxenberg
Contributor
July 16, 2025

Would love to get an answer for this as well, what's the point of concurrent dependency if it is still marked as broken? 

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events