In some cases (see below), dependencies are marked as broken even though the settings allow concurrent dependencies.
Settings/Context: concurrent dependencies are allowed:
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):
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!
Would love to get an answer for this as well, what's the point of concurrent dependency if it is still marked as broken?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.