This list may include some issues incorrectly, because "p4 fixes -i" does not report a fix for a version branch if the files changed by the fix were deleted on the masters before the version branch was taken.
| Job | Priority | Title |
|---|---|---|
| job000029 | nice | Filespecs and fixes aren't replicated properly from TeamTrack to Perforce |
| job000031 | essential | Queries to TeamTrack database may fail because of unescaped quotes in SQL |
| job000033 | essential | Incompatible with other TeamShare API programs |
| job000048 | essential | Consistency checking of the configuration is inadequate |
| job000063 | essential | Dates aren't replicated with fixes |
| job000075 | essential | No automatic check of configuration |
| job000076 | optional | Deleting records gives the replicator a headache |
| job000098 | optional | Perforce UIs don't link to defect tracker UIs |
| job000099 | optional | The p4 module has a security hole |
| job000148 | essential | Replicator is slow due to reading auxiliary tables many times |
| job000152 | nice | "commenton" parameters not enforced by Bugzilla integration |
| job000154 | nice | "shadowdb" is not supported by the Bugzilla integration |
| job000156 | essential | Pending changelists aren't clearly indicated as such in Bugzilla |
| job000169 | optional | Change numbers are links in TeamTrack even when no changelist URL has been specified |
| job000175 | nice | System fields like P4DTI-rid are editable by users in Perforce |
| job000182 | essential | Elapsed time fields aren't replicated properly |
| job000188 | essential | The TeamTrack integration fails with non-ASCII characters |
| job000194 | essential | Perforce states include tSupport states as well as tTrack states |
| job000196 | optional | Illegal transitions should be prevented by Perforce clients |
| job000197 | optional | P4DTI doesn't do ESMTP authentication |
| job000201 | nice | Empty assigned_to field can't be replicated (unreproducible) |
| job000207 | optional | Deleted jobs aren't restored immediately |
| job000212 | essential | TeamTrack 4.5 not supported |
| job000213 | optional | Performance of Bugzilla is reduced because it always locks tables |
| job000220 | optional | Perforce admin/superuser password is in clear in config.py |
| job000223 | optional | Quote in change comment terminates display in TeamTrack |
| job000233 | essential | When you submit a new issue to TeamTrack it overwrites the issue |
| job000239 | optional | The jobname function not configurable |
| job000242 | optional | Uninstalling the RPM before running the P4DTI fails |
| job000250 | nice | If you run the refresh script as your first step, all issues get overwritten |
| job000264 | optional | Uninstalling RPM-installed P4DTI doesn't remove symlinks |
| job000298 | essential | Multiple Perforce sections in the Bugzilla form |
| job000302 | essential | Test procedure doesn't test P4DTI upgrade |
| job000305 | essential | tTrack: mystery empty transition failure |
| job000311 | essential | If you have two TeamTrack projects with the same name, the replicator stops working |
| job000318 | optional | "p4 logger" failed once |
| job000320 | essential | P4DTI is not tested on Solaris |
| job000322 | nice | Type checking is too strict |
| job000323 | nice | If you use "python -G" to run the P4DTI you don't get so much error checking |
| job000325 | critical | Can't read issues from TeamTrack 5.0 |
| job000328 | critical | Queries with plus or percent signs fail in TeamTrack 5.0 |
| job000335 | critical | Can't update cases in a TeamTrack 5.0 database |
| job000338 | critical | TeamTrack 5.0 doesn't update P4DTI_ fields |
| job000339 | essential | Can lose Bugzilla changes in rare race condition |
| job000344 | optional | Bugzilla fixes table not sorted by changelist |
| job000346 | essential | Can't stop replication of an issue |
| job000348 | optional | Bugzilla comments can get wrong timestamp |
| job000350 | essential | Can't update some Bugzilla fields from Perforce |
| job000353 | nice | Bugzilla's formatted views don't show P4DTI information |
| job000365 | optional | No startup script for Solaris |
| job000366 | essential | Some replicator failures may leave things inconsistent |
| job000367 | optional | Stopping using the startup script can cause inconsistencies |
| job000369 | optional | Integration Kit is hard to build and test |
| job000370 | critical | Journal fields in TeamTrack 5.0 can't be replicated |
| job000379 | critical | P4DTI corrupts date/time fields in TeamTrack if server time zone is not UTC |
| job000380 | essential | Bugzilla integration upgrade fails if you change the replicator id |
| job000387 | essential | TeamTrack 5.0 integration doesn't provide good error messages |
| job000391 | nice | Can't build Bugzilla integration from kit |
| job000396 | essential | Bugzilla 2.14 integration doesn't send notification e-mails |
| job000397 | optional | Obscure error message when Perforce client incompatible with server |
| job000412 | optional | Can't migrate users from Perforce to TeamTrack automatically |
| job000414 | optional | Bugzilla integration is slow if many users don't match up |
| job000417 | nice | If you change replicated_fields and forget to refresh then fields may be mixed up in Perforce |
| job000423 | optional | Bugzilla integration may fail due to MySQL IntegrityError |
| job000432 | nice | Debugging information not available when customer makes a support call |
| job000434 | essential | Migration of nonexistent users is too cumbersome |
| job000435 | nice | Bugzilla doesn't have enough fields to migrate typical jobs |
| job000437 | essential | Jobspec not suitable for creating new jobs |
| job000438 | optional | Have to create Bugzilla products/components/versions by hand when migrating |
| job000439 | essential | Migration documentation is hard to find |
| job000443 | essential | Replicator needlessly re-does work |
| job000444 | essential | P4DTI can generate a lot of conflict email messages very quickly |
| job000460 | essential | P4DTI not known to support unicode |
| job000473 | optional | Bugzilla integration doesn't check MySQL server version |
| job000479 | nice | P4DTI fails to run as a service on Windows NT (unreproducible) |
| job000481 | essential | TeamTrack transition not replicated from P4D 2002.1 beta (29455) on submit of pending changelist |
| job000482 | essential | P4DTI Windows Service stalls after a few days |
| job000484 | optional | Bugzilla integration fails to update timestamp if only description changes |
| job000485 | essential | Too many conflict e-mails sent |
| job000486 | optional | Exponential backoff looks like failure |
| job000487 | essential | Documentation doesn't troubleshoot poll failure very well |
| job000488 | essential | AG doesn't stress importance of not deleting issues |
| job000489 | optional | Mail recipients are not very configurable |
| job000497 | optional | Bugzilla can't replicate lastdiffed field if we run processmail |
| job000498 | essential | Bugzilla integration doesn't treat "numeric" fields well |
| job000501 | essential | new jobs break TeamTrack integration if LASTMODIFIEDDATE or SUBMITDATE are replicated |
| job000518 | optional | migrate_users doesn't add the P4DTI user to Bugzilla |
| job000523 | essential | Bugzilla user interface doesn't tolerate missing changelist records |
| job000524 | optional | It's hard to force the replication of particular items to the defect tracker |
| job000525 | essential | Consistency checker doesn't check changelists. |
| job000597 | nice | Test suite doesn't give error for invalid Bugzilla admin user |
| job000606 | optional | Test suite doesn't display config file name |
| job000607 | essential | Bugzilla 2.16.1 not supported |
| job000611 | essential | TeamTrack test database licenses expired |
| job000613 | essential | TeamTrack interface MSVC workspace is confused |
| job000614 | essential | TeamTrack tests run when configured for Bugzilla on Windows |
| job000615 | essential | Bugzilla shows extra changelists with multiple Perforce servers |
| job000618 | optional | Automated release build script requires client with release/... |
| job000628 | critical | Bugzilla 2.16 and 2.16.1 patches are broken |
| job000629 | optional | Sense of release notes "what's new" is reversed |
| job000630 | essential | Can't restrict State field values by TeamTrack project |
| job000638 | optional | "p4dti subsystem is locked" message from startup script |
| job000697 | essential | Bugzilla 2.18 not supported |
| job000701 | essential | A hanging query can lock up the defect tracker |
| job000705 | essential | Insufficient documentation for running tests |
| job000706 | optional | Procedure for running a single test does not (always?) work. |
| job000707 | optional | Automated tests can't cope if dbms_password is needed. |
| job000708 | optional | No procedure for creating new mysql dumps |
| job000757 | essential | Issue script doesn't segregate TeamTrack jobs |
| job000815 | optional | Perl warnings generated when test suite runs Bugzilla scripts |
| job000840 | essential | Documentation refers to TeamShare, not Serena |
| job000864 | optional | Change to fix user not replicated |
| job000900 | optional | When installing service, get "Fatal Python error: PyThreadState_Get: no current thread" |
| job000956 | essential | No P4DTI section when Bz 2.16+ bug is "formatted for printing" |
| job000969 | essential | No support for Perforce "tickets" |
| job000972 | essential | Enormous changelist descriptions break replication to Bugzilla |
| job000975 | essential | User guide does not mention P4V |
| job000977 | critical | perforce documentation links in UG do not work. |
| job001054 | optional | AG has no job_url example for P4Web |
| job001256 | essential | No warning message if bugzilla_directory set to None |
| job001258 | essential | Bugzilla 'deadline' field not replicated. |
| job001259 | essential | P4DTI can't handle new Bugzilla 'enum' tables |
| job001260 | essential | P4DTI can't handle null fields in Bugzilla |
| job001261 | essential | test suite breaks MySQL on Windows |
| job001262 | optional | test suite doesn't work with Bugzilla 2.20 checksetup on Windows |
| job001263 | essential | P4DTI doesn't support Bugzilla 2.20. |
| job001264 | optional | Obsolete Bugzilla versions still supported |
| job001268 | essential | Component version documentation/testing is out-of-date |
| job001272 | essential | Manuals refer to old Perforce documentation |
| job001292 | optional | Integration Kit can't make a distribution |
| job001469 | essential | Python Windows extensions requirement not documented |
| job001689 | essential | Bugzilla 3.0 not supported |
| job001690 | essential | Update set of supported Bugzilla releases |
| job001691 | critical | new Bugzilla parameter access breaks P4DTI patch |
| job001692 | essential | Bugzilla 3.0 not recognised by P4DTI replicator |
| job001693 | essential | Single-select custom fields not replicated correctly |
| job001694 | essential | Bad names for custom fields |
| job001695 | essential | Perforce section not appearing in Bugzilla 3.0 bug form |
| job001696 | essential | Recent MySQLdb releases not supported |
| job001697 | essential | MySQL 5.0 breaks P4DTI |
| job001698 | essential | Bugzilla field name change breaks P4DTI |
| job001699 | essential | MySQL 5.0 doesn't like 0 in datetime fields |
| job001700 | optional | MySQL 5.0 complains at non-default fields |
| job001701 | essential | P4DTI build script too slow |
| job001702 | essential | build script doesn't check dependencies |
| job001703 | essential | release build script requires winzip |
| job002051 | essential | MySQLdb version testing doesn't check for unicode support |
| job002052 | essential | Can't output Unicode content in log messages |
| job002053 | essential | Unicode replication fails |
| job002055 | optional | Unnecessary warnings during user and issue migration |
| job002056 | optional | Build script assumes winzip |
| job002084 | essential | P4DTI does no MySQL version detection |
| job002086 | essential | Perforce server Unicode mode detection inadequate |
| job002295 | essential | P4DTI doesn't work with Python 2.6 |