Jira Plan - Scheduling Dependencies with configuration for Sequential or Concurrent

[Harvindar Singh]

In the Jira Plan Summary page, Jira Plan is reporting 10 blocked issues.

When I select it and view the filter it indicates "Issues with overlapping dates" selected in the filter (per below screenshot):

The current configuration is set to Sequential:

This in my opinion explains the issue for example when dependent tickets are planned in the same sprint.

I thought if I changed to the configuration to Concurrent that the issues raised by Jira Plan would be fixed but when I make that change, the same warning from Jira Plan remains.

I need to find out how this Dependencies configuration is meant to work for Jira Plan.

[Harvindar Singh · Accepted solution]

I think I've answered my own question in the reply below :)

[Trudy Claspill]

Hello @Harvindar Singh 

I'm not sure how the Blocked summary is intended to work with regard to the two types of Dependencies schedule options, but I did find there is an open issue regarding that aspect of the summary.

https://jira.atlassian.com/browse/JRACLOUD-91463

[Harvindar Singh]

Thanks @Trudy Claspill for the pointer. The issue reported refers to the issue count discrepancy between that reported by the Summary page compared to the TimeLine view.

I investigated further and found the following which might provide the answer to the open issue above. Note I have a combination of Blocked and Dependent link types.
Summary page reports 15 Blocked issues today. This uses the Filter = Issues with overlapping dates.
Note following issue counts when the following configurations are used in Plan settings:
- If Scheduling -> Dependencies is set to Concurrent = 9 issues selected
- If Scheduling -> Dependencies is set to Sequential = 15 issues selected
Technically speaking all 15 issues satisfy the filter condition but when Concurrent is set, the issues satisfying this second condition i.e. scheduled at the same time, are no longer counted. This would occur for dependent issues planned in the same sprint.