|Title||TeamShare API error reporting is inadequate|
|Assigned user||Gareth Rees|
|Description||When TeamTrack refuses to update or transition an issue because a user doesn't have the privilege to do so, it raises an error but provides only an empty error message. The replicator can't provide any information to the user to explain why the operation failed.|
|Analysis||This problem is present in the TeamTrack API version 1.2.|
It is essential that this defect is fixed, otherwise it will be very hard to make the integration reliable.
There are other problems with error reporting in the TeamShare API; see "TeamShare API comments".
|Evidence||[GDR 2000-09-11] "TeamShare API comments"; Gareth Rees; 2000-09-11: <URL: |
|Created by||Gareth Rees|
|Created on||2000-09-13 18:41:31|
|Last modified by||Gareth Rees|
|Last modified on||2010-10-06 21:20:12|
|History||2000-09-13 GDR Created.|
2000-11-28 RB Added priority. Moved text to description.
2000-12-07 GDR Improved description.
2001-02-14 GDR Closed. Error messages much improved in TeamTrack build 4407.
|7949||closed||2001-02-01 22:13:23||Gareth Rees||Updated the TeamTrack integration so that it works with (and requires) TeamTrack build 4407. This involved the following changes:
1. Use the new TeamTrack API, as of 2001-01-15.
2. Edited TSServer::ValidateVersion() so that it doesn't hang when connecting. See job000190.
3. Increased the supported_dbver parameter to 27, to match TeamTrack 4407.
4. Updated the Administrator's Guide so that it requires 4407.