Issue Summary

This issue is bordering on bug and enhancement territory. 

If you use the quick add story on the dependency page, it will auto populate the feature with the feature that is assigned to the dependency.  This can result in a story assigned to a team in a different program than the feature, which can cause sync issues.

Ideally, the feature selector on the dependency quick add page would function similarly to how it works on the regular story creation page, where features in other programs do not appear (unless it is a multi-program feature).  

The feature assigned to the story should be blank by default, and the available list should be filtered according to the team or program that is selected.

Steps to Reproduce

The following steps assume that you have 2 separate programs with working features, PIs, sprints, and agile teams.  I'll refer to them as program A and program B.

1. Create a dependency in Program A, linked to a feature in Program A.  Team A depends on Team B (from Program B)
2. Open the dependency just created and click on the + add button under Assigned Stories.

Expected Results

The blank story page should not already be populated with a feature.  The parent feature of this story should be selected after the appropriate Program and Team have been chosen.

Actual Results

The assigned feature is automatically pre-populated with the feature that is assigned to the dependency.  Depending on the intended program and team of the story, this may not be correct and could cause sync issues if this story is created under a feature in a different program.

Workaround

It is possible to manually remove the feature and assign the correct feature.  However, we shouldn't expect users to need to do that.  We also shouldn't be allowing users to create work items through the UI that are never going to be able to sync.