| Title | Resolution fields aren't handled by Bugzilla integration |
| Status | closed |
| Priority | critical |
| Assigned user | Nick Barnes |
| Organization | Ravenbrook |
| Description | In Bugzilla there is a "resolution" field as well as a "status" field. When the status becomes "RESOLVED", the resolution field has to acquire a value (one of a small set). When the status becomes "REOPENED", the resolution field has to be cleared. Neither of these things happens if the status is changed by the replicator. The resolution field is not currently replicated to Perforce. Note that one possible resolution is "DUPLICATE", of another bug whose number is given in a separate field. |
| Analysis | The resolution field should be replicated to Perforce. The jobspec should allow these values: Fixed, Invalid, WontFix, Later, Remind, WorksForMe, Duplicate. Using Perforce to resolve a bug as a duplicate should not be supported; the matching Bugzilla activity is rather complex (adding comments to the longdescs table for two separate bugs). bugzilla_bug.update needs some changes to support this: If the status is being changed: If the new status is RESOLVED: If the resolution is blank and not being changed: change the resolution to FIXED. Else if the new status is REOPENED: Change the resolution to '' |
| How found | inspection |
| Evidence | I just know. |
| Introduced in | 0.5.0 |
| Created by | Nick Barnes |
| Created on | 2000-11-29 14:40:25 |
| Last modified by | Gareth Rees |
| Last modified on | 2001-12-10 19:05:35 |
| History | 2000-11-29 NB Created. |
| Change | Effect | Date | User | Description |
|---|---|---|---|---|
| 5369 | closed | 2000-12-04 14:30:39 | Nick Barnes | Resolved job job000091. |