Ravenbrook / Projects / Perforce Defect Tracking Integration / Issues
| Job | Priority | Title |
|---|---|---|
| job000522 | essential | P4DTI may fail if Perforce client exists and is broken |
| job000627 | essential | P4DTI supports TeamTrack, but Perforce doesn't |
| job000692 | essential | replicate_p documentation needs more examples |
| job000693 | essential | Changing rid and running refresh script causes confusion |
| job000694 | essential | check_jobs doesn't work on Windows if .py file association is set |
| 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 |
Generated at 2013-05-21 05:03:17 by $Id: //info.ravenbrook.com/infosys/cgi/issue.cgi#476 $
Copyright © Ravenbrook Limited. This document is provided "as is", without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this document. You may make and distribute verbatim copies of this document provided that you do not charge a fee for this document or for its distribution.