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
Hi everyone, We’re always looking at how to improve Confluence and customer feedback plays an important role in making sure we're investing in the areas that will bring the most value to the most c...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.