|Title||Can't easily add to replicated_fields list|
|Assigned user||Gareth Rees|
|Description||The configurator doesn't cope if you change the replicated_fields.|
The P4DTI administrator can't add a new field to the replicated_fields list (except at the end of that list) because the new field will get a Perforce field number that was previously used by another field. So the data that was previously in that other field gets captured by the new field.
If you have used the automatic configuration generator and you edit the replicated_fields list, fields probably get the wrong values in Perforce, because the generated jobspec's field numbers probably don't match the old values.
|Analysis||The automatic configuration generator for TeamTrack generates jobspec fields in the order given in the replicated_fields list. This means that if you insert a new field in the middle of this list, the fields that follow the new field get new field numbers in the jobspec, and so capture the data that previously belonged to other fields.|
The automatic configuration generator could read the jobspec and make sure that fields keep their numbers where this is possible, and to warn where it is not.
Alternatively, suggests RB, the user could specify the field numbers.
Or maybe the configurator could just warn when a field changes its number.
We could either:
1. Advise people to delete all their jobs and re-replicate whenever they change the replicated_fields list.
2. Support specifying the Perforce field number in the replicated_field list, for example replicated_fields = [('DESCRIPTION', 110), ('PRIORITY', 111)].
3. Automatically delete all the jobs and re-replicate in case (1).
We adopted solution (1) and documented the problem. GDR 2001-02-15.
|Evidence||Spotted when I added a field to the replicated_fields list.|
See configure_teamtrack.py or configure_bugzilla.py.
|Created by||Gareth Rees|
|Created on||2000-11-30 16:02:20|
|Last modified by||Gareth Rees|
|Last modified on||2001-12-10 19:07:10|
|History||2000-11-30 GDR Created. Agreed priority with RB.|
2000-12-08 RB Upgraded to "essential" and merged in duplicate job job000141. Added suggestion 3.
2001-02-15 GDR Set to closed.
|7930||closed||2001-02-01 16:06:20||Richard Brooksby||Added missing information to section 9, "Maintaining the P4DTI", and clarified some of the existing instructions.|