Comment 1 for bug 655819

Brad and I discussed this issue in the original review. We could update the view to ignore the field since we know the value is not needed, but I think the form is confusing though. Updating the UI to deactivate the field would be best--the user can see the old value and know it is not being used, but knows he can change his mind.