P4DTI issue job000280

TitleIssue name changes in TeamTrack not reflected in Perforce
Assigned userGareth Rees
DescriptionYou can change the name of an issue in TeamTrack by changing its issue type. However, the job remains unchanged. So the issue might have started out as BUG00123, and then be changed to ENH00123, but it's still replicated to BUG00123 in Perforce. The P4DTI TeamTrack integration is now maintained and supported by TeamShare <http://www.teamshare.com/>.
AnalysisYou can't change the name of a job in Perforce: the name is the key in the database. Could possibly delete the old job and re-replicate. (This would delete the old fixes and then add corresponding fixes to the new job.)
This feature in TeamTrack is poor: an attribute of an issue (i.e. its type) shouldn't be part of its name: the name should be a permanent key to the issue.
How foundmanual_test
EvidenceFound during testing of 1.0.6.
Observed in1.0.6
Created byGareth Rees
Created on2001-03-25 13:59:43
Last modified byDavid Jones
Last modified on2003-08-19 13:55:16
History2001-03-25 GDR Created.
2003-05-19 NB TeamShare handover.
2003-08-19 DRJ Suspended due to teamshare handover


Change Effect Date User Description
35521 suspended 2002-11-14 13:44:46 Richard Brooksby Removing TeamTrack support from master sources.
Updating project index and FAQ to reflect new TeamTrack situation.