Private Views: Ensure EWM:WorkItem link rules applied consistently, regardless of Change Set origin

Currently Views are treated differently by type:

• Shared: Requires Change Sets explicitly be created by User and is delivered with same mechanics of any other Change Set based Change*
• Personal: Change Sets are automatically created and delivered, disregarding EWM: WorkItem Linking requirements against the Stream.

*Note: I've not confirmed conflict resolution behavior of Shared Views, though presume it's the same as any other Artifact change.

Issues are with any change to Personal Views (Edit, Delete, or Create).

We've a dual Stream change management strategy (Dev Stream for edits, Master Stream for changes approved via formal review). While Change Set delivery disregards EWM: WorkItem rules for delivery against the Parent Stream of the Change Set (Dev Stream), subsequently delivering these to the Master Stream is beholden to the EWM: WorkItem Linking requirement. This prevents View Change Sets from being further delivered to Master. Over time, this creates the problem of an ever growing number of View Change Sets being created and stuck undelivered to the Master. Worse, these Views are often identified as Dependencies to Change Sets we're trying to deliver to Master so there is a rapidly growing number of Views cluttering the delivery process, all of which need to be manually unchecked when attempting to deliver (as the default for custom delivery is for all dependencies to be prechecked, which can now number over 100+ of these limbo Views, and growing).

This runaway noise of Views stuck in limbo needs to be addressed. Either:

1. Be true to the GUI wording and NOT have Personal Views use Change Sets for its updates.
2. Change the behavior of Views Change Sets to disregard EWM:WorkItem linking requirements, regardless of the origins of the Change Set (e.g. ensure it's disregarded when attempting to deliver changes from the Dev Stream to its Parent, Master Stream).

NOTE: May be implemented via an additional check box in the Stream Details present to the User when either Change Set linked to EWM:WorkItem (i.e. change request) required options set (though, this is a setting which should be Process Shared between Project Areas).

3. Provide a setting option (ideally at the Project Area level, able to be Process Shared between Project Areas), eliminating the behavior exception provided to the Personal Views (i.e. requiring the User explicitly Create and Deliver the Change Set, regardless of type of View.