| Title | Implicit changes made by the DT don't get replicated back |
| Status | closed |
| Priority | essential |
| Assigned user | Gareth Rees |
| Organization | Ravenbrook |
| Description | If the DT makes a change to a field because of a rule for a transition, the replicator doesn't notice and replicate that change back to Perforce. For example, TeamTrack changes the owner on certain transitions, but the change of owner isn't replicated back to the Perforce job. |
| Analysis | GDR says that the replicator needs to re-read the changes table to pick up any implicit changes and replicate them back. In practice it's simpler and probably more robust to just fetch the issue after replicating the job and see if it differs from what we expect it to look like. TeamShare claim that all automatic changes get put in the CHANGES table, but it's nice not to depend on that. |
| How found | manual_test |
| Evidence | <http://www.ravenbrook.com/project/p4dti/doc/2000-10-31/mahi-alpha-test/> item 4 |
| Observed in | 0.3.2 |
| Test procedure | <http://www.ravenbrook.com/project/p4dti/master/test/test_p4dti.py>, section 10 |
| Created by | Richard Brooksby |
| Created on | 2000-11-22 11:36:11 |
| Last modified by | Gareth Rees |
| Last modified on | 2001-12-10 19:01:50 |
| History | 2000-11-22 RB Created from sources (see evidence). 2000-11-30 GDR Fixed and closed. |
| Change | Effect | Date | User | Description |
|---|---|---|---|---|
| 5186 | closed | 2000-11-30 16:21:48 | Gareth Rees | Replicating implicit changes in the defect tracker back to Perforce. |