User Problem

As per the existing design, Dependencies are not directly tied to the Portfolio through associated Programs or Teams. Instead, they are linked to the Portfolio via the Program Increment. This means that while Dependencies can involve multiple Programs across different Portfolios, their settings are determined by their specific Program Increments, not by the Portfolio where they are created.

Suggested Solutions

To improve the user experience, it's suggested that the settings for Dependencies be directly associated with the Portfolio in which they are created.

Current Workarounds

At present, no workarounds have been identified for this particular design behavior.