Jira Portfolio cyclical dependency

[Ron_McFarlane]

Hi I am having an issue scheduling a story in Jira portfolio. The story has 2 warnings

1. Violation in dependency.

A required work item could not be scheduled.

2. This issue can't be scheduled due to a cyclic dependency

This issue depends on an issue that directly (or indirectly) depends back on this issue. Remove that dependency and recalculate your plan.

This story has 2 sub tasks

There is a link between the sub tasks

Subtask 1 blocks subtask 2

Subtask 1 is higher in the backlog than subtask 2

Subtask 1 has the error

Violation in dependency.

A required work item could not be scheduled.

If I complete subtask 1 first then I can do subtask 2. It should be scheduled that way as subtask 1 is higher on the priority list.

I can't see the cyclical dependency on this. 

If I remove the link there there is no problem.

Why would Portfolio think there is an issue?

Thanks

[Shannon Spaniol]

Hello Ron,

There's a known suggestion for this below:

• JPOSERVER-1600 Allow Subtask to have dependency to other Subtask

Please vote on the request above and comment with your usage case, as it helps to properly address the desired feature.

Regards,

Shannon