| Title | Consistency checker may miss some issues if you change the start date |
| Status | closed |
| Priority | essential |
| Assigned user | Nick Barnes |
| Organization | Ravenbrook |
| Description | If an issue is being replicated, but hasn't changed since the start_date, then the consistency checker will claim to find an inconsistency. This can happen if you move the start_date forward in time and possibly in other ways. |
| Analysis | The all_issues method of the defect_tracker classes is currently specified to return all issues changed since the start date which are either unreplicated or are replicated by this replicator. In fact it should return _all_ issues being replicated by this replicator, regardless of start date, and all _unreplicated_ issues changed since the start date. At present, if an issue which hasn't changed since the start date is being replicated, the all_issues won't return it and so the consistency checker won't check it. In contrast, the consistency checker checks all _jobs_ which are replicated by this replicator. |
| How found | inspection |
| Evidence | Thinking about code on the migration branch. |
| Observed in | 1.1.1 |
| Introduced in | 1.0.0 |
| Test procedure | <http://www.ravenbrook.com/project/p4dti/master/test/test_p4dti.py>, section 8.2 |
| Created by | Nick Barnes |
| Created on | 2001-06-27 14:57:59 |
| Last modified by | Gareth Rees |
| Last modified on | 2001-12-10 19:46:50 |
| History | 2001-06-27 NB Created |
| Change | Effect | Date | User | Description |
|---|---|---|---|---|
| 13581 | closed | 2001-06-27 15:29:01 | Nick Barnes | Change the specification of defect_tracker.all_issues. See job000340. |