Known issues in P4DTI release 1.0.0

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
job000016 essential Double replication causes many conflicts
job000022 essential No migration from Perforce jobs to defect tracker
job000027 critical There are outstanding defects that were found in release 0.3.0
job000030 optional Users can't get help based on messages
job000036 optional New jobs in Perforce don't get replicated to the defect tracker
job000042 essential Rapid changes in the DT cause conflicts
job000046 essential The replicator process is hard to manage
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
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
job000086 optional Users can "fix" issues that they don't have permission to change
job000114 optional There's no description of the limitations of the integration
job000124 essential Changes by disabled Bugzilla users may be replicated
job000125 optional Bugzilla version not checked
job000128 essential Can't replicate fix to deleted changelist
job000134 essential The replicator log grows without limit
job000135 essential Replicator makes no more progress if replication to Perforce fails
job000137 essential Documentation doesn't explain why fixes don't get undone with other changes
job000145 essential Deleted TeamTrack states appear in Perforce jobspec
job000148 essential Replicator is slow due to reading auxiliary tables many times
job000149 essential We don't use system logging facilities on Windows
job000151 optional Source code documentation is inadequate
job000159 essential Fixes which the replicator rejects still get replicated
job000162 optional Replicator needs restarting when you add new users to Perforce or TeamTrack
job000166 essential MySQLdb version 0.3.0 is untested
job000167 optional Released manuals should be on the website
job000171 nice AG should note broken MySQL versions
job000174 essential No instructions on how to upgrade from the beta
job000179 nice Teamtrack.dll can get lost
job000188 essential The TeamTrack integration fails with non-ASCII characters
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
job000203 nice Users can masquerade as other users
job000208 optional TeamTrack integration doesn't provide a .reg file
job000210 optional Bugzilla states/resolutions with spaces in them cause broken jobspec
job000211 optional Mail can get lost
job000215 essential The replicator can send out mail bombs
job000216 optional readme.txt mentions beta sites
job000217 critical readme.txt has too much detail of fixed bugs
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
job000221 critical Refreshing Perforce jobs fails in Bugzilla integration
job000222 essential Deleting fix causes Bugzilla integration to crash
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
job000227 optional AG doesn't have Bugzilla error messages
job000228 essential UG text is somewhat specific to TeamTrack
job000229 essential The readme is too hard to use
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
job000233 essential When you submit a new issue to TeamTrack it overwrites the issue
job000234 critical Jobs from Bugzilla get wrong name
job000235 critical New Bugzilla bugs may cause conflict email
job000236 critical Bugzilla table grows without bound
job000237 critical Bugzilla logger breaks on Windows
job000238 critical Bugzilla integration doesn't work with old Python versions
job000240 optional Perforce server can crash if P4DTI is started with existing jobs
job000241 critical Bugzilla integration doesn't work with MySQL version 3.22.32
job000243 essential The p4 client is not on path when running from RPM install
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
job000252 essential Support can't detect tampering with P4DTI source
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
job000261 critical Bugzilla patch and text files are missing from the RPM installation
job000262 essential Bugzilla: Can't use Perforce to confirm an unconfirmed bug
job000263 essential Bugzilla: P4DTI doesn't restart on reboot
job000265 essential AG doesn't say to stop the replicator using the startup script
job000267 optional Consistency check may complain about Bugzilla bugs which are OK
job000268 essential Screenshots in UG are out of date with respect to TeamTrack
job000270 critical Can't fix job owned by user (None) in the TeamTrack integration
job000271 essential The migrate script loses fixes
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
job000281 optional Lists of jobs fixed in release notes is incomplete
job000283 critical Bugzilla integration may fail on startup on a fast server
job000284 critical No build procedure for the Integration Kit
job000285 essential No introduction or roadmap to the Integration Kit
job000286 optional AG doesn't state what systems each integration supports
job000287 critical The P4DTI doesn't include an integration kit
job000288 essential Can't upgrade Bugzilla integration cleanly
job000289 optional Users with spaces produce confusing errors
job000290 essential The release build procedure's instructions on submission can't be followed
job000293 optional AG doesn't discuss operating stand-alone
job000295 critical Unmatched Bugzilla users break replicator at startup
job000296 essential Release build procedure can generate incorrect list of fixed issues
job000301 essential Manuals refer to, which is inaccessible to the world
job000304 essential If replication fails, reverting may also fail
job000305 essential tTrack: mystery empty transition failure
job000306 essential Bugzilla integration holds locks after errors
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
job000312 essential P4DTI doesn't support Bugzilla 2.12
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
job000317 optional Error message is unhelpful when you're using an unsupported version of the MySQLdb module
job000321 optional TeamTrack server fails when memory is low.
job000324 essential Bugzilla patch doesn't work well on Solaris 8
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
job000329 optional Risk of losing configuration when upgrading the P4DTI
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
job000340 essential Consistency checker may miss some issues if you change the start date
job000342 optional User's Guide has incorrect link to P4SAG
job000343 essential When using multiple Perforce servers, TeamTrack uses wrong changelist link
job000344 optional Bugzilla fixes table not sorted by changelist
job000345 critical New Bugzilla bugs don't get replicated for some users
job000347 essential Upgrading to a new release of the P4DTI is awkward and error-prone
job000349 optional No way to link to job web page from defect tracker
job000351 essential Bugzilla integration doesn't remove old configuration items
job000352 essential Bugzilla emailsuffix parameter not supported
job000354 critical MySQL bug stops replicator from seeing some Bugzilla changes
job000359 essential Startup e-mail is misleading in TeamTrack integration
job000360 optional Bugzilla configuration starts with dt_name="TeamTrack"
job000364 essential Bugzilla bugs with empty descriptions can't be replicated
job000375 critical Whitespace lines in Bugzilla descriptions can break replicator
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
job000384 nice P4DTI will stop working in Python 3.0
job000385 critical Renumbered changelist causes P4DTI error and deletes fix
job000388 optional Error reporting is poor if you choose not to receive e-mail
job000389 essential Bugzilla integration not supported on Windows
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
job000403 optional Instructions on how to select issues to replicate are inadequate
job000404 nice No startup message if you don't receive e-mail
job000405 essential Configuration section in AG needs improvement
job000406 critical MySQL integrity error when you create a new bug in Bugzilla and update it quickly
job000409 essential Not clear if TeamTrack 5.01 is supported or not
job000410 essential Can't confirm an unconfirmed Bugzilla bug from Perforce
job000411 critical Bugzilla integration depends on MySQLdb returning lists
job000413 essential Bugzilla integration does not work with MySQLdb 0.9.0 or later
job000427 optional Can't delete associated filespec in Bugzilla integration
job000433 critical TeamTrack 5.02 not supported
job000442 essential Can't replicate 'line' fields with hashes in them to Perforce
job000445 essential Bugzilla replicator doesn't like spaces in enum fields
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
job000463 critical Bugzilla integration fails if mx.DateTime module is installed
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
job000693 essential Changing rid and running refresh script causes confusion
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
job000704 essential Bugzilla fixes table shows the fixer, not the changer
job000756 essential MySQL privilege required and not documented
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
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