We have a number of projects, most of which contain two areas: Documentation and Software. Occasionally, the project in which a bug occurs is not clear (our customers typically deploy a suite of interoperable products we supply which interact with third-party software and hardware, which complicates troubleshooting to the extent that front-line support staff cannot always determine where the root cause of a problem lies).
When we change the project, the area is reset to the first in the alphabetical list of areas, which usually goes unnoticed. In our case, since the bulk of our problems are software-related, the fact that Documentation occurs before Software in the dictionary means misleading information can easily appear in our FogBugz installation.
The following behavior would be preferable:
(1) If the new project contains the same list of areas as the first project, the new area should match that of the originally-selected area.
(2) If there is no matching area, the default area should be configurable per project rather than relying on an accident of alphabetization.
(3) (per cdeszak's suggestion below) Some visual indication if the area is changed due to editing the project.
