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 |
|---|---|---|
| job000006 | essential | TeamShare API error reporting is inadequate |
| job000007 | critical | The fixes keyword can't be set on submit (except to "closed") |
| job000010 | essential | "p4 -G client -o" sometimes fails |
| job000013 | critical | Deleting fixes not replicated |
| job000014 | essential | Edited filespecs aren't replicated from TeamTrack to Perforce |
| job000015 | critical | TeamTrack creates filespec entries in the TS_VACATIONS table with the wrong value in the TS_TIME2 field |
| job000016 | essential | Double replication causes many conflicts |
| job000017 | essential | If you add a field to the Perforce jobspec, then "p4 -G job -o jobname" fails |
| job000024 | optional | "\012" appears in fixes table in TeamTrack instead of newline |
| job000027 | critical | There are outstanding defects that were found in release 0.3.0 |
| job000030 | optional | Users can't get help based on messages |
| job000032 | optional | Deletion of fixes and filespecs in TeamTrack may cease to work in future releases |
| job000033 | essential | Incompatible with other TeamShare API programs |
| job000036 | optional | New jobs in Perforce don't get replicated to the defect tracker |
| job000042 | essential | Rapid changes in the DT cause conflicts |
| job000043 | essential | There's no way to prevent changes by rules |
| job000046 | essential | The replicator process is hard to manage |
| job000047 | essential | Historical bugs are replicated but uninteresting |
| job000048 | essential | Consistency checking of the configuration is inadequate |
| job000050 | essential | There's no way to re-start replication |
| job000052 | optional | Likely problems not in troubleshooting section |
| job000054 | essential | There are few reports |
| job000065 | essential | Not enough logging control |
| job000066 | optional | We don't explain which jobspecs won't work |
| job000075 | essential | No automatic check of configuration |
| job000077 | essential | UG contains no version or release related documentation |
| job000078 | nice | Replication failure can cause hard-to-recover database records when using advanced configuration |
| job000082 | essential | AG has no training and documentation section |
| job000084 | optional | No glossary in the UG |
| job000086 | optional | Users can "fix" issues that they don't have permission to change |
| job000097 | critical | Replicated fixes and filespecs not visible from Bugzilla |
| job000101 | optional | Different transitions for different issue types may confuse the replicator |
| job000103 | essential | Can't easily add to replicated_fields list |
| job000108 | essential | Userids can't differ between TeamTrack and Perforce |
| job000109 | essential | Can't get at Perforce information from TeamTrack |
| job000112 | essential | Can't easily replicate by project |
| job000114 | optional | There's no description of the limitations of the integration |
| job000117 | essential | Jobview and job filter confused in the UG |
| job000119 | essential | The Perforce commands "change -s" and "submit -s" aren't explained in the UG |
| job000121 | essential | E-mail messages are hard to read |
| job000122 | essential | Server failures aren't handled gracefully |
| job000124 | essential | Changes by disabled Bugzilla users may be replicated |
| job000126 | optional | Documentation tells people to use command line to see fixes |
| job000127 | critical | Can't submit changelist with fix in P4Win 2000.2 |
| job000128 | essential | Can't replicate fix to deleted changelist |
| job000130 | essential | UG should say "p4 submit -s" not "p4 submit" |
| job000131 | essential | The UG is confusing |
| job000132 | essential | Supported platforms unclear |
| job000133 | critical | You can't close a job by fixing it |
| job000134 | essential | The replicator log grows without limit |
| job000135 | essential | Replicator makes no more progress if replication to Perforce fails |
| job000136 | optional | Unclear where the data lives |
| job000137 | essential | Documentation doesn't explain why fixes don't get undone with other changes |
| job000138 | essential | "Add Job Fix" always sends jobs to "closed" |
| job000140 | nice | Logical field name "code" not allowed in TeamTrack |
| job000141 | essential | Can't add to replicated_fields list |
| job000143 | critical | Document histories missing from sources |
| job000144 | essential | "ignore" can't be a job status |
| job000145 | essential | Deleted TeamTrack states appear in Perforce jobspec |
| job000146 | essential | Empty date fields in TeamTrack give the replicator a headache |
| job000147 | essential | TeamTrack licence available but not mentioned |
| job000148 | essential | Replicator is slow due to reading auxiliary tables many times |
| job000149 | essential | We don't use system logging facilities on Windows |
| job000150 | critical | The replicator can't recover from server failures |
| job000151 | optional | Source code documentation is inadequate |
| job000158 | essential | Obscure error if Perforce can't be reached or p4_client_executable is wrong |
| job000159 | essential | Fixes which the replicator rejects still get replicated |
| job000161 | nice | Replicator appears to hang |
| job000162 | optional | Replicator needs restarting when you add new users to Perforce or TeamTrack |
| job000167 | optional | Released manuals should be on the website |
| job000169 | optional | Change numbers are links in TeamTrack even when no changelist URL has been specified |
| job000170 | optional | Replicator may be unable to send e-mail if the default replicator_address is unchanged |
| job000173 | essential | Wrong Perforce server version causes installation to fail mysteriously |
| job000178 | essential | AG doesn't give advice on making problem reports |
| job000179 | nice | Teamtrack.dll can get lost |
| job000181 | critical | Assertion failure in translate_1_to_0 |
| job000182 | essential | Elapsed time fields aren't replicated properly |
| job000188 | essential | The TeamTrack integration fails with non-ASCII characters |
| job000189 | essential | The replicated_fields parameter can't be changed without replicating all jobs |
| job000190 | critical | Connection to TeamTrack hangs for several minutes |
| job000191 | essential | Administrator can't easily find release when contacting support |
| job000194 | essential | Perforce states include tSupport states as well as tTrack states |
| job000195 | essential | Keyword translation is too conservative |
| job000200 | critical | No supported TeamTrack release works with integration |
| job000202 | essential | Errors from Perforce not reported well |
| job000203 | nice | Users can masquerade as other users |
| job000204 | essential | Issue owned by non-existent Perforce user causes crash |
| job000205 | critical | Configuration is still too difficult |
| job000208 | optional | TeamTrack integration doesn't provide a .reg file |
| job000211 | optional | Mail can get lost |
| job000212 | essential | TeamTrack 4.5 not supported |
| job000214 | essential | No way of controlling the poll period |
| job000215 | essential | The replicator can send out mail bombs |
| job000218 | critical | readme.txt has a confusing date at the top |
| job000219 | essential | Existing jobs in Perforce may become unusable when the jobspec is changed |
| job000223 | optional | Quote in change comment terminates display in TeamTrack |
| job000225 | essential | If you "p4 fix" when there's no closed state, the replicator can't replicate |
| job000226 | optional | Newlines don't show up in change descriptions in TeamTrack |
| job000228 | essential | UG text is somewhat specific to TeamTrack |
| job000230 | essential | Messages from the replicator refer to non-existent sections of the manuals |
| job000232 | optional | Log and e-mail messages are confusing if jobname is different from the issue name |
| job000240 | optional | Perforce server can crash if P4DTI is started with existing jobs |
| job000244 | essential | TeamTrack names the wrong user in an error message |
| job000245 | essential | Unhelpful error from TeamTrack if you can't edit an issue |
| job000249 | essential | Refresh script fails if you change the closed_state |
| job000251 | essential | Known issues included in release notes |
| job000253 | essential | Can't "add fix" to submitted changelist except to "closed" in P4Win |
| job000254 | essential | AG claims TeamShare support provide licences |
| job000257 | optional | AG uses wrong words when talking about Perforce licences and support |
| job000276 | optional | Can't fix (and then delete the fix) a job owned by user (None) in the TeamTrack integration |
| job000277 | critical | Consistency checker and refresh script don't work with larger TeamTrack databases |
| job000278 | essential | Migrating jobs to TeamTrack fails if there are many jobs |
| job000286 | optional | AG doesn't state what systems each integration supports |
| job000287 | critical | The P4DTI doesn't include an integration kit |
| job000293 | optional | AG doesn't discuss operating stand-alone |
| job000301 | essential | Manuals refer to info.ravenbrook.com, which is inaccessible to the world |
| job000304 | essential | If replication fails, reverting may also fail |
| job000305 | essential | tTrack: mystery empty transition failure |
| job000308 | essential | No error or warning when user mapping isn't one to one |
| job000309 | essential | Underscores don't work in Perforce jobviews |
| job000310 | essential | TeamTrack 5.0 is not supported |
| job000311 | essential | If you have two TeamTrack projects with the same name, the replicator stops working |
| job000313 | essential | If you spell a job with the wrong case when making a fix, the replicator can't replicate it |
| job000316 | optional | User mismatch not documented |
| job000321 | optional | TeamTrack server fails when memory is low. |
| job000325 | critical | Can't read issues from TeamTrack 5.0 |
| job000326 | critical | Can't update cases in a TeamTrack database upgraded from 4.5 to 5.0 |
| job000328 | critical | Queries with plus or percent signs fail in TeamTrack 5.0 |
| job000333 | optional | Poor error message from TeamTrack 5.0 when you specify wrong user or password |
| job000334 | critical | Intermittent socket errors from TeamTrack 5.0 when using a database upgraded from TeamTrack 4.5 |
| job000335 | critical | Can't update cases in a TeamTrack 5.0 database |
| job000337 | optional | Replicator fails to pair up users if their e-mail addresses differ only in case |
| job000338 | critical | TeamTrack 5.0 doesn't update P4DTI_ fields |
| job000343 | essential | When using multiple Perforce servers, TeamTrack uses wrong changelist link |
| job000349 | optional | No way to link to job web page from defect tracker |
| job000376 | essential | In TeamTrack integration, P4Win crashes if you try to create a job |
| job000377 | essential | Can't use Perforce 2000.2 client with Perforce 2001.1 server |
| job000378 | essential | Hard to work out which TeamTrack field types are supported |
| job000379 | critical | P4DTI corrupts date/time fields in TeamTrack if server time zone is not UTC |
| job000381 | critical | P4DTI corrupts date/time fields in TeamTrack if daylight savings time is in effect |
| job000382 | essential | "[Errno 5] Input/output error" from Bugzilla integration logger |
| job000383 | essential | AG needs better description of TeamTrack workflows that don't work with the P4DTI |
| job000385 | critical | Renumbered changelist causes P4DTI error and deletes fix |
| job000388 | optional | Error reporting is poor if you choose not to receive e-mail |
| job000390 | critical | P4DTI doesn't support Bugzilla 2.14 |
| job000398 | essential | May get conflicts after running the refresh script |
| job000399 | essential | Some issue titles can't be replicated |
| job000405 | essential | Configuration section in AG needs improvement |
| job000409 | essential | Not clear if TeamTrack 5.01 is supported or not |
| job000433 | critical | TeamTrack 5.02 not supported |
| job000442 | essential | Can't replicate 'line' fields with hashes in them to Perforce |
| job000447 | critical | Bugzilla 2.14.1 not supported |
| job000453 | critical | Perforce 2002.1 not supported |
| job000459 | critical | TeamTrack 5.5 not supported |
| job000460 | essential | P4DTI not known to support unicode |
| job000461 | critical | Bugzilla integration doesn't support multiple Perforce servers |
| job000478 | essential | TeamTrack 5.02 is supported |
| 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 |
| job000522 | essential | P4DTI may fail if Perforce client exists and is broken |
| job000533 | essential | p4_user with wrong email address confuses Bugzilla user translator |
| job000596 | essential | Automatic test expects a bug to replicate on first poll |
| job000607 | essential | Bugzilla 2.16.1 not supported |
| job000608 | essential | Bugzilla 2.14 security patch releases not supported. |
| job000609 | essential | Test suite for Bugzilla on Windows doesn't work |
| job000610 | essential | Bugzilla/Windows integration doesn't support processmail |
| job000612 | optional | Bugzilla integration doesn't check use_windows_event_log config parameter |
| 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 |
| job000616 | optional | Linux/Unix system log usage not configurable |
| job000617 | optional | Test suite not very useful under Python 2.2 |
| job000624 | essential | Licence still says copyright 2001. |
| job000629 | optional | Sense of release notes "what's new" is reversed |
| job000630 | essential | Can't restrict State field values by TeamTrack project |
| job000692 | essential | replicate_p documentation needs more examples |
| job000695 | essential | AG doesn't specify using P4 'admin' access level |
| job000696 | essential | P4DTI documentation covers old defect tracker versions |
| job000698 | essential | P4DTI installation docs are lengthy and confusing |
| job000699 | essential | P4DTI doesn't allow customizable jobspec |
| job000700 | essential | Perforce user password is disclosed on command line |
| job000828 | optional | "licence" should read "license" |
| job000830 | essential | No way to check the jobspec |
| job000831 | essential | No way to just extend the jobspec |
| job000832 | nice | P4DTI checksum script doesn't know jobspec scripts |
| job000833 | essential | Bugzilla 2.16.4 not supported. |
| job000907 | essential | UG makes incorrect statements about p4 change "-s" option |
| job000963 | essential | P4DTI does not support Bugzilla 2.18 |
| job000964 | essential | Bugzilla emails give incorrect values for user fields |
| 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 |
| 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 |