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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

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

0 votes

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. 



0 votes



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!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Advanced Roadmaps

3 short videos to help you get started with Advanced Roadmaps

Hi community, I’m Roi, a product manager working on Advanced Roadmaps for Jira. While Advanced Roadmaps is a powerful tool to plan and track work at scale, we know it can be challenging to get star...

6,512 views 25 18
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you