If you are importing data from Excel using the Web Admin interface (Application Administrator) Import Data function, you may experience hangs, even on a single record. The problem might be related to the field used for uniqueness checking, as there is an internal limit on this field when used to track imports . The simplest workaround is to use a different field to check for uniqueness (a numeric field for preference), or not to check at all (which allows the import to complete).
One TeamTrack/Business Mashup system's data is import to another TeamTrack/Business Mashups instance; when the change history comes over, the transition for any transition which loops back to the same state it came from will show up in the destination as the generic "Updated" instead of the actual looping transition's name. This is also true of the submit transition, just showing "Submitted" instead of the actual submit transition's name.
If you export requirements to an XML file and then just reimport them without any changes, you will sometimes get failures where HTML attributes are used, for example: COMPONENT_REQUIREMENTS COMP_000007 Failed Mandatory attribute value is missing for attribute named: TEXT This only seems to be an issue if the class was created pre-2009R1.
When in " Import users from LDAP" in the Application Administrator, clicking the Refresh button under the Find Candidates section more than one time before the information is returned can cause IIS CPU usage to spike and the system to hang .
