P4DTI issue job000129

TitlePending changelists aren't clearly indicated as such in TeamTrack
Statusclosed
Priorityessential
Assigned userGareth Rees
Productproject
OrganizationTeamShare
DescriptionYou can't tell the difference in TeamTrack's Version Control History section between a pending changelist and a submitted one. This means that you might mistakenly think that work has been done when in fact it is only pending and may later be reverted.
AnalysisThe information is there in the VCACTIONS table -- the INFO2 field in a changelist record contains a bit that indicates if the changelist is pending. So TeamTrack can display the information.
I suggest putting (pending) after the change number for pending changes. This makes it as clear as possible which are pending.
See <http://info.ravenbrook.com/mail/2000/12/05/22-01-10/0.txt> for my suggested layout for the fixes table in TeamTrack. GDR 2000-12-06.
How foundmanual_test
Evidence<http://www.ravenbrook.com/project/p4dt...ign/teamtrack-p4dti-schema/#section-3.4>
<http://info.ravenbrook.com/mail/2000/12/05/22-01-10/0.txt>
Observed in0.4.0
Created byGareth Rees
Created on2000-12-05 21:52:25
Last modified byGareth Rees
Last modified on2001-12-10 19:10:33
History2000-12-05 GDR Created.
2000-12-06 GDR Referenced e-mail.
2001-02-14 GDR Closed. Fixed in TeamTrack build 4407.

Fixes

Change Effect Date User Description
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.