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 |
job000148 | essential | Replicator is slow due to reading auxiliary tables many times |
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 |
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 |
job000212 | essential | TeamTrack 4.5 not supported |
job000223 | optional | Quote in change comment terminates display in TeamTrack |
job000233 | essential | When you submit a new issue to TeamTrack it overwrites the issue |
job000305 | essential | tTrack: mystery empty transition failure |
job000311 | essential | If you have two TeamTrack projects with the same name, the replicator stops working |
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 |
job000344 | optional | Bugzilla fixes table not sorted by changelist |
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 |
job000387 | essential | TeamTrack 5.0 integration doesn't provide good error messages |
job000396 | essential | Bugzilla 2.14 integration doesn't send notification e-mails |
job000412 | optional | Can't migrate users from Perforce to TeamTrack automatically |
job000437 | essential | Jobspec not suitable for creating new jobs |
job000460 | essential | P4DTI not known to support unicode |
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 |
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 |
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 |
job000629 | optional | Sense of release notes "what's new" is reversed |
job000630 | essential | Can't restrict State field values by TeamTrack project |
job000757 | essential | Issue script doesn't segregate TeamTrack jobs |
job000764 | essential | Test suite fails with Bugzilla versions 2.16.1 to 2.16.3 |
job000841 | essential | Test suite warnings with Python 2.3 |
job000842 | critical | Python 2.3 or 2.3.x breaks Bugzilla integration |
job000907 | essential | UG makes incorrect statements about p4 change "-s" option |
job000948 | essential | New Bugzilla groups system not supported |
job000949 | essential | Can't handle new Bugzilla product and component tables |
job000955 | optional | P4DTI section not using Bugzilla template hooks |
job000958 | essential | Bugzilla schema doc is out of date |
job000959 | optional | P4DTI doesn't work with Bugzilla 2.17.x |
job000963 | essential | P4DTI does not support Bugzilla 2.18 |
job000964 | essential | Bugzilla emails give incorrect values for user fields |
job000965 | essential | User Guide is out-of-date about Perforce interfaces |
job000968 | essential | Interactions with Perforce ticket system not documented |
job000971 | essential | No P4DTI section when Bz 2.17+ bug is "formatted for printing" |
job000975 | essential | User guide does not mention P4V |
job001098 | essential | Python 2.4 breaks p4.py |
job001119 | essential | Can't run as Windows Service with Python 2.4 |
job001120 | optional | Bugzilla schema documentation doesn't cover recent versions |
job001121 | essential | P4DTI doesn't support Bugzilla 2.16.7. |
job001122 | optional | P4DTI not tested against Bugzilla 2.18rc3. |
job001123 | essential | No Bugzilla 2.18 support |
job001124 | essential | P4DTI doesn't support Bugzilla 2.16.8. |
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 |
job001268 | essential | Component version documentation/testing is out-of-date |
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 |
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 |
job002084 | essential | P4DTI does no MySQL version detection |
job002086 | essential | Perforce server Unicode mode detection inadequate |