nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Tickets're not shown in portfolio dependencies when dependencies are not in the same release.

Legna Garcia

Hi Folks,

When dependencies are not in the same release, they are not shown.
Even if changing the release version, it doesn't come up.

This is a high risk since we may are missing some dependencies from portfolio repot.

How can I solve this? any ideas?

Regards,

Accepted answers

Legna Garcia

Hi folks,

I had an analysis discussion with Support People. If you are experiencing the same behavior, here is the sumary of the result :

1. The boards/projects selected as the source for the Portfolio plan didn't have that linked issues within them. : for checking this, go to the issue that doesn't appear in the report, and click on "View on board" link, and make sure you add the issue the correspondent board or even add the correct board in portfolio plan settings. The difference between choosing a board as a source and a project is that the project will return all issues related to it and the board, the board's filter outcome issues.

2. The issue appears in Scope option. So after board changes are done, and you are sure the portfolio resourses are correctly configured, hit Calculate from the "scope" view. The issue started to appear in the Scope and in the Dependencies report.

I hope this helps, it worked to us

Regards,

All comments

Shannon S

Hi Legna,

It seems that you might be running into this bug:

JPOCLOUD-1994

Can you have a look and confirm?

The dependency report does not list dependencies of a certain issue link type, even though it is properly configured in Portfolio's Dependency Settings

This happens for dependencies that are swapped, i.e., the dependency type description reads

If A <something> B, then B is scheduled before A

and not ...then A is scheduled before B

These dependencies are still properly respected by the scheduling algorithm and also show up in the issue details page and schedule tooltip but they are missing in the dependency report.

Regards,

Shannon

Legna Garcia

Hi @Shannon S: no, it looks like a different issue since it is nothing related with the swaping link.

Shannon S

Legna,

Thank you for confirming that. I'm creating a ticket now for you with the Cloud Support team, so they can have a better look at your issue from their end.

Once the issue is determined, please feel free to reply on this thread with the resolution or if it's an existing bug. This will help users in the future if they run into the same problem.

Regards,

Shannon

Legna Garcia

Sure! This is impacting a lot our projects and I'll be pending on the investigation result.

Thanks!

Legna Garcia

Hi folks,

I had an analysis discussion with Support People. If you are experiencing the same behavior, here is the sumary of the result :

I hope this helps, it worked to us

Regards,

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-cloud

advanced-roadmaps