Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Circular Dependencies in Portfolio

Hello,

I am using Jira Portfolio and would like to understand how to resolve the Circular Dependency error. I have looked through the documentation and have not found an example of how to remove or fix the Circular Dependency error. Any guidance or assistance with the matter would greatly be appreciated.  Below is a link that I have used in my research at this time.

Thank you,

https://confluence.atlassian.com/jiraportfoliocloud/using-scope-and-dependencies-828785260.html

1 answer

0 votes
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 10, 2018

Hello,

A Circular Dependency happens when an issue effectively blocks itself on a Logic conflict.  The most basic scenario occurs when an issue is blocked by and blocks the same issue.

But a more complex scenario is:

  • issue ABC-1 blocks ABC-2,  and ABC-2 blocks ABC-3
  • ABC-1 must be complete before ABC-2, and ABC-2 before ABC-3
  • Then the Circular referance come in when ABC-3 also blocks ABC-1 so that effectively ABC-1, 2 and 3 need to be complete before ABC-1 can be started, so ABC-1 is blocking itself from starting.

To locate these issues you will need to look at the issue details in the scope panel to identify the Dependencies flagged with a cyclic dependency violation and manually look for the logic conflict point and remove the dependency causing the loop back for the desired order.

Removing the ABC-3 blocks ABC-1 dependency would schedule in the order 1,2,3

Removing the ABC-2 Blocks ABC-3 dependency would schedule the issues 3,1,2

Removing the ABC-1 Blocks ABC-2 dependency would schedule the issues 2,3,1

-Earl

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events