If you use Jira Cloud please read all of this note. The files in this depot location are a development build patch to P4DTG 2018.1 for job101543 and other jobs. This bug may affect Jira Cloud and on-premise Jira installations. job101543 stops all replication. All features/fixes in this build will be in the next release of P4DTG and have been tested. When the next release of P4DTG is available you should install that. Sample errors in the logs (log-MAPNAME.log or jira-rest-NNNNNN.log.N) for job101543: Feb 24, 2020 11:08:45 AM com.perforce.p4dtg.plugin.jira.tcp.internal.request.RequestHandler queryDefects SEVERE: RestClientException{statusCode=Optional.absent(), errorCollections=[]} or Caused by: org.codehaus.jettison.json.JSONException: JSONObject["name"] not found. or INFO: RestClientException in hasProjectAccess("CDS"): org.codehaus.jettison.json.JSONException: JSONObject["names"] not found. RestClientException{statusCode=Optional.absent(), errorCollections=[]} --------------------------------------- To deploy: This build requires java 1.8 or later. Stop replication Move these two files somewhere else (do not just rename): <p4dtg-install>/jira/jira-rest.jar <p4dtg-install>/jira/jira-rest-all-dependencies.jar Replace the jira-rest.jar file in the jira subdirectory. jira-rest-all-dependencies.jar should be removed. Assure the file protections allow read and execute of the jar. Start replication --------------------------------------- Notes for Jira's Assignee and Reporter: Jira Cloud does not have a "user name" like Jira on premises does so P4DTG 2018.1 could not replicate Jira's Assignee and Reporter. This patch can retrieve user alternate identifiers: email, short email (before "@"), or Display name. IMPORTANT NOTE: Jira Cloud Account security can limit the plugin's access to your email. Individuals control access to their account's email in their Jira Account settings. If you find your Display Name is replicated, security is the likely cause. The replicated User information attempts to find a value. The default fields we check are: "name,email,emailshort,displayname" which works for both Jira on premises and Jira Cloud. To change the ordering, add a <UserStyle> element to jira-rest-config.xml. Sample: <Config> <JiraHandling> <UserStyle>name,emailshort,email,displayname</UserStyle> </JiraHandling> -------------------------------------------------------------------------------- Minor new functionality in 202X.X #2196053 (Bug #78504) Technical Preview: Allow setting the SocketTimeout, ConnectionTimeout, and RequestTimeout in jira-rest-config.xml's JiraHandling element. #2192436 (Bug #104586) Many other issue fields can now be replicated by first defining the fields in jira-rest-config.xml as custom fields. For example, "Time Spent" can now be copied to the job. #2192415 (Bug #88895) JIRA Label fields can now be copied to the Perforce job. The reverse direction (job to JIRA) is not supported. -------------------------------------------------------------------------------- Bugs fixed in 202X.X #2577325 (Bug #119935) For Jira Data Center (on-premises), a Personal Access Token (PAT) is now supported. For user, enter "*" and put the PAT into the password. #2553477 (Bug #119134) Generated JQL now correctly quotes custom field names. #2267863 (Bug #110065) Projects with a key that's a JQL keyword will now replicate #2265719 (Bug #109986) The Jira java process startup will no longer use -XXUseConcMarkSweepGC. #1950284 (Bug #102150) Jira Cloud can now replicate JIRA's Assignee and Reporter fields. Only a "copy to" Perforce is supported. See jira-rest-config.xml. #1925907 (Bug #101543) Updated Atlassian Java client library to support Jira Cloud. Creating Jira Cloud Issues is not supported. #2240881 The Jira (SOAP) plugin has been removed. Please migrate to the JIRA-REST plugin.
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#4 | 30280 | Joel Brown |
Update for additional bug fixes coming in the next release of P4DTG. See the Readme for fixes included. |
||
#3 | 26482 | Joel Brown |
Jira cloud patch update: handle Assignee, Reporter. The probelm was caused by a behavior difference between Jira cloud and Jira on premises. |
||
#2 | 26358 | Joel Brown | Mention that java 1.8 is required | ||
#1 | 26357 | Joel Brown | Development build for fix for job101543. |