You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi,
I am new here and hope that I can contribute some day but until then - I have a few questions. Hope you guys can help me.
I work as a Product Owner with Portfolio 3.19 and have a question regarding dependency links.
When I create a dependency link to an issue outside of my project (project A) and move the issue in project A so that will influence the the issue in the other project (project B) after saving those changes I get a red dot on that issue (indicates a change) WITHIN project A portfolio.
But in the project B portfolio the changes won't be shown in the first place until I actively click on the link dot in the issue. Then the dot link turns red.
This is not really convenient because when you have a lot of dependencies and they all change, you end up clicking each dot only to check if there was a change.
Is this a bug? I have not seen this behaviour when having the same scenario WITHIN ONLY ONE PROJECT. Here changing one issue with dependency to another will result in a red dot indication in both issues.