You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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
Hello Ron,
There's a known suggestion for this below:
Please vote on the request above and comment with your usage case, as it helps to properly address the desired feature.
Regards,
Shannon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.