Jump to content


Tubah

Member Since 04 May 2012
Offline Last Active Sep 01 2017 03:27 AM
-----

Posts I've Made

In Topic: P4DTG/JIRA-REST and moved Issues

01 September 2017 - 03:30 AM

Common questions/problem..

Sorry, no easy way to move issues.  Once moved, p4dtg just notices the new issue and it is unaware of the old.

the only way is to disallow moving by mortals.

Then, to move an issue between projects you should:
* shut down p4dtg
* move the issue, get the new issue id
* rename the job to your new project-id name.  You can't  technically rename jobs:  you create a new one and delete the old.  May be complicated if fixes are attached.
* in the renamed job, also edit the DTG_DTISSUE to the new issue id.
* restart p4dtg

If they were in different segments, than implies different DTG_MAPID values so you would also have to adjust that.

In Topic: Where to get p42db

15 March 2017 - 11:44 PM

Make sure you check out http://answers.perfo...rticles/KB/2727

In Topic: p4dtg changelist writeback problem

15 March 2017 - 11:42 PM

regarding the

In the KB  P4DTG JIRA Troubleshooting  set the flag for -Djavadts.DUMP_DEBUG=true for the jira source.
This logs to the jira-rest-XXXXX.log.0 file.

Set the mapping's attribute logging level to 3 if not already.

Restart replication.  

In a browser, login into JIRA with the p4dtg user ('perforce') used in jira source.

Update/create an issue in JIRA.   Examine the actual JQL queries in the jira-rest-*.log file.

Cut & paste that JQL into an jira advanced query (while still logged into JIRA as the p4dtg user).

Does that then work or not?