Issue Summary

The "Need By" field is marked as required in the Detail Panel Settings for the portfolio for Dependencies. However, when creating the Dependency through "Create" tab or from Program Level(without selecting a PI in the left navigation), we are able to see the "Need By" field as required only after selecting a PI and an Associated Feature/Requesting Team.

The Dependency is tied to the Portfolio settings through the Program increment.
This behavior is true when a dependency is added from the Program level and a PI is selected from the left navigation, by clicking on "Add Dependencies", the "Needed by" field appears mandatory as expected.

Steps to Reproduce

• Ensure Needed By is selected as a required field for Dependency in the Details Panels Settings tab
• Navigate to Program
• Do not select a PI in the left navigation
• Navigate to Dependency and click on "Add Dependency"
• Notice that the "Needed By" field is not populated as mandatory field
• Select an Associated Feature or set a requesting team
• Notice that now the "Needed By" field is populated as required
• This is also true when creating Dependency from the "Create" tab.

Expected Results

If "Need By" field as set as required under Details Panels Settings for Dependency for a Portfolio, while adding a Dependency, the "Needed By" field should be populated as required after selecting a Program Increment.

Actual Results

If "Need By" field as set as required under Details Panels Settings for Dependency for a Portfolio, while adding a Dependency, the "Needed By" field is populated as required only after selecting a Program Increment and an Associated Feature/Requesting Team. This happens when a creating the dependency from the "create" tab or through Program level provided there is no Program increment selected in the left navigation.

Workaround

Currently the work around available is to have the Dependency created through Program level by selecting the appropriate PI on the left navigation.