In all other inputs to TFS (Team Explorer, TWA, etc.), System.State data is manipulated on input and forced to a specific case (e.g. 'Closed', 'Active', etc. - i.e. Pascal Case With Spaces), but when using Excel Bulk Update, TFS allows the System.State data to be saved in any case chosen by the user (e.g. 'closed', 'cLoSEd', 'aCTIVE', etc.)
There doesn't seem to be any negative impact to TFS other than cosmetic, since the TFS API typically treats those values as case insensitive. However, it has caused problems for us since we have built custom tools and reports while being unaware of this issue and are now uncovering sleeping bugs when the case of System.State data becomes 'corrupted' in this manner.
Is this a known issue or bug? If so are there any plans to change this behavior to be consistent with the other TFS UIs?