The Perforce Defect Tracking Gateway (P4DTG) allows information to be shared between Perforce's basic defect tracking system called jobs and an external defect tracking system. A job typically represents an enhancement request or a bug to be fixed. The relationship between jobs and the external system is created using the graphical configuration editor. Propagation of the data between the two systems is coordinated by the replication engine.

Details

Easily installed and configured

All the technology necessary to implement an integrated solution comes built into P4DTG. The mapping of fields between a defect tracking system and jobs is easily defined using a visual configuration editor. The editor includes the ability to map data sets contained in multi-value listboxes with point and click accuracy. The one-way or two-way replication of data can be implemented on a field by field basis.

Automatically propagates changes

A built-in replication engine insures updates to the defect tracking system and Perforce jobs are synchronized. Changelists, which Perforce uses to describe the work and list the files involved in addressing a job, can also be replicated.

Support for Mercury's Quality Center 9.0

P4DTG comes with a plug-in for Mercury's Quality Center 9.0.

An SDK is now available that allows customers and vendors to develop integrations to support commercial and in-house defect tracking systems. For more information about the P4DTG SDK please contact partners@perforce.com.

Legacy integrations available with P4DTI

Perforce will continue to support its existing Bugzilla integration that is implemented with the Perforce Defect Tracking Integration (P4DTI) technology. For more information on P4DTI please view the Perforce Defect Tracking Integration page.