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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Confgured dependencies are not shown in the portfolio report

Hi folks,

The dependencies report is showing up only tickets which issue link is a "Block", even if I have configured "Dependency" issue link into the list, the dependencies report remains showing up only dependencies with "block".  Why Portfolio is not showing up the configured issue links for this purpose?

Thanks in advance!

3 answers

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



This issue was brought up with Atlassian Support and we wanted to make sure the information wast relayed here incase anyone else is seeing this behavior.


This issue turned out to be a new BUG in Portfolio on Jira Cloud instances and the bug report can be viewed here:

That's correct. Thanks @Earl McCutcheon. I posted a comment regarding to increase the priority of this bug. This is affecting dependencies management for our PMs.

Thanks in advance!

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

Hello Legna,

Details on configuring the dependencies in portfolio can be found at the following Links:

- Managing portfolio dependencies

- Dependencies report

As noted "In Portfolio for Jira, the block dependency is set by default", but additional dependencies need to be associated.

First confirm that you have the additional dependencies set under portfolio administration, and if you have the settings configured as described in the documentation you may be running into the following BUG if you are on a 2.10 or earlier version of portfolio Where there is a conflict between the inward and outward facing issue links:

If this is not the case I would recommend reaching out to Atlassian Support so we can take a closer look at the specifics of the plan to help narrow this down for you.

Hi @Earl McCutcheon


Thanks for answering.  I have tried by adding "dependent" link, but even if I don't swap them, the dependencies report only show up the block dependency links.

I'll reach out Atlassian Support team. 



Is there a fixed bug already? someone who can help with this?  thanks in advance. 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events