Issue Summary

Setting the "Required" toggle for Stories under Details Panel Settings for Dependencies does not seem to do anything. The user is not prevented from creating or modifying a dependency if this toggle is enabled.

Steps to Reproduce

As an admin user:
1) Navigate to Administration > Settings > Details Panel Settings
2) Select a Portfolio
3) Select Dependencies for the Work Item.
4) Locate the Stories Toggle and enable it. Also, enable the Required Toggle and Save the changes.
5) Navigate to the Dependencies Grid and make sure the portfolio you used to set the Details Panel settings is configured in Tier 1.
6) Create a dependency against a Feature - add all of the other required information.
7) Save the Dependency
8) Alternatively, open an existing dependency against a feature and note the assigned stories section. Either remove any existing stories or don't add any at all and click the save button.

Expected Results

If Stories is a required field for Dependencies, throw an error message if the user neglects to add one.

Actual Results

The user can save a Dependency without having to add stories. Furthermore, there doesn't seem to be a Story field available when creating a new dependency, nor is it clear if the "Assigned Stories" field is the actual Story field from the Details panel settings

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available