Jump to content


Member Since 04 May 2012
Offline Last Active Feb 15 2017 09:04 PM

Posts I've Made

In Topic: Using P4DTG with multiple bug tracking packages

08 November 2016 - 01:19 AM

You need to segment (filter) your Perforce source.


In Topic: Whitespaces added to scripts

19 July 2016 - 04:28 PM

Check your versions and the file's perforce type.  There was a bug where type 'utf8' files, submitted with a <=15.1 client on windows, to an early 2015.2 server, would introduce extra CR into the file.

In Topic: BOM issue in unicode mode server

12 July 2016 - 10:25 PM

I replied in stackoverflow.

In Topic: P4 commands not working

04 May 2016 - 11:38 PM

Add p4.exe to your path?

The default in earlier windows is under Program Files, eg c:\Program Files\Perforce\

DId you even install p4?  Can grab the "Helix P4: Command-Line" from https://www.perforce...s/helix#clients

In Topic: How to use P4DTG to map p4 changelist to Jira Activity field like 'P4 Cha...

14 April 2016 - 04:55 PM

I assume you're using the JIRA-REST plugin.

In the Perforce section (lower left), select Fix Details and click Copy to Defect tracker.

For the "copy-to" dialog of JIRA (defect tracker) fields, select FIX.  "Fix" is a dtg implemented field that will add a Comment with the changelist info.

You can also append the changelist info to a JIRA "text" field.  If you have a custom field for this, you can "copy to" that and it will append.   If your customer field does not appear in the copy-to dialog, note that your custom field must be added to jira-rest-config.xml so that it is of type "TEXT" and access "RW".   Need to check the connection (or restart p4dtg-config) to pick up changes to jira-rest-config.xml.

Appending to a jira large text field or adding comments are your only options.