Allow only one option for configuring integration approach

[mirvin]

I propose that we force user to use the Assign defects to user approach instead of offering two approaches. This would mitigate the damage to platform support cycles caused by these

1. Paralysis from Analysis - Many customers don't understand the implications of using either approach and so they seek more documentation to help them understand more. I have only empirical data but I have observed almost every Bugzilla customer that I have had to have a phone conference with, could not determine why they should use tagged over assigned approaches and have asked me which one I felt strongest about using. I anticipate yet another while I am writing this issue.
2. The are 4 Tagged fields. It increases the probability of error just by virtue of the reduction of possible data entry fields. This could be remedied by more robust field validation but I am for the reduction of complexity as opposed growing the configtool.
   a. The custom field needed by this integration approach could be an issue if the configurator is not an admin
   b. User enter the strangest values here. Again, robust app could solve this.
3. User attempt to combine the two approaches. This could be addressed by code polishing.

The only way that this integration can afford to have many configuration paths given that it creates so many undocumented and unpredictable states is that we attach constraints to some of the fields on the form and create more descriptive documentation that highlights the happy path.

[ibuchanan]

I wholly agree with the overall suggestion of having only 1 approach. And I agree with your points 1 and 3. But I beg to differ on the simplicity of the assigned approach over the tagged approach. Your point 2 may be true for configuration but I think it ignores day-to-day usage. It requires the person configuring the integration to explain to all his users that assignment has been "overloaded" with an integration function that is not at all obvious from typical usage of Bugzilla. The additional field of the tagged approach makes the transition to VersionOne more explicit and obvious.

Of course, both are limited by what can be done inside Bugzilla. Maybe we need to step back and reconsider both configuration and usage, which may lead us to yet another integration approach. But, if it did, then we should use that only, not just add it on.