This is a guest post written by Randy DeFauw. Randy is a technical marketing manager at Perforce. He has over 10 years
of experience in software configuration management using a variety of products
and SEI/CMMI Level 5 software engineering practices.

Over at Perforce HQ, we’re always looking for new and better ways to integrate Perforce with the tools that our users know and love. We’re proud to announce our release of a robust integration between Perforce and Jira (4.1 and later), in the framework of our Defect Tracking Gateway (DTG).

Two-way integration

The DTG provides a fast, scalable integration architecture. Issues in Jira are replicated to Perforce as jobs, and job updates in Perforce can be sent back to Jira. The DTG can be configured to send a selection of fields and translate field values between Jira and Perforce. Fields can be replicated from Jira to Perforce, from Perforce to Jira, or in both directions. More importantly, fix information is replicated into the Jira issue, as shown in the screenshot below.

figure 1v2.png

Changelist information in Jira


The DTG also lets you pick which issues are replicated, using the Jira project or some other field as a filter.

figure 2.png

Replication configuration


Once the jobs are in Perforce, you can use all of the normal Perforce tools to link changelists to jobs, see which jobs are assigned to you in P4V, and search through jobs.

figure 3.png

Jira information in P4V


Learn More

Best of all, the DTG is a fully supported Perforce product, so you can count on our world-class technical support.

Two great tools just got better – check out the new Jira DTG plugin today! Learn more about the Jira integration, or contact me with any questions at

Integrate Perforce with Jira